Skip to content

[unitest] small change in test_deepgemm_precision.py#7834

Open
zhoutianzi666 wants to merge 6 commits into
PaddlePaddle:developfrom
zhoutianzi666:make_time_more_precisi
Open

[unitest] small change in test_deepgemm_precision.py#7834
zhoutianzi666 wants to merge 6 commits into
PaddlePaddle:developfrom
zhoutianzi666:make_time_more_precisi

Conversation

@zhoutianzi666
Copy link
Copy Markdown
Collaborator

Motivation

💡 If this PR is a Cherry Pick, the PR title needs to follow the format by adding the [Cherry-Pick] label at the very beginning and appending the original PR ID at the end. For example, [Cherry-Pick][CI] Add check trigger and logic(#5191)

💡 如若此PR是Cherry Pick,PR标题需遵循格式,在最开始加上[Cherry-Pick]标签,以及最后面加上原PR ID,例如[Cherry-Pick][CI] Add check trigger and logic(#5191)

Modifications

Usage or Command

Accuracy Tests

Checklist

  • Add at least a tag in the PR title.
    • Tag list: [[FDConfig],[APIServer],[Engine], [Scheduler], [PD Disaggregation], [Executor], [Graph Optimization], [Speculative Decoding], [RL], [Models], [Quantization], [Loader], [OP], [KVCache], [DataProcessor], [BugFix], [Docs], [CI], [Optimization], [Feature], [Benchmark], [Others], [XPU], [HPU], [GCU], [DCU], [Iluvatar], [Metax]]
    • You can add new tags based on the PR content, but the semantics must be clear.
  • Format your code, run pre-commit before commit.
  • Add unit tests. Please write the reason in this PR if no unit tests.
  • Provide accuracy results.
  • If the current PR is submitting to the release branch, make sure the PR has been submitted to the develop branch, then cherry-pick it to the release branch with the [Cherry-Pick] PR tag.

PaddlePaddle-bot

This comment was marked as outdated.

@codecov-commenter
Copy link
Copy Markdown

codecov-commenter commented May 15, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (develop@79dd64a). Learn more about missing BASE report.

Additional details and impacted files
@@            Coverage Diff             @@
##             develop    #7834   +/-   ##
==========================================
  Coverage           ?   63.27%           
==========================================
  Files              ?      462           
  Lines              ?    64276           
  Branches           ?     9851           
==========================================
  Hits               ?    40670           
  Misses             ?    20841           
  Partials           ?     2765           
Flag Coverage Δ
GPU 72.38% <ø> (?)
XPU 7.12% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@PaddlePaddle-bot
Copy link
Copy Markdown

PaddlePaddle-bot commented May 15, 2026

🤖 Paddle-CI-Agent | ci_status_monitor | 2026-05-18 11:51:59

CI报告基于以下代码生成(30分钟更新一次):


1 任务总览

✅ 所有 Required 任务全部通过,PR 可合入。

总执行(rerun次数) 总任务 ✅ 通过 ❌ 失败 ⏳ 运行中 ⏸️ 等待中 跳过
42(0) 42 39 3 0 0 0

2 任务状态汇总

2.1 Required任务 : 10/10 通过

必选任务阻塞合并,失败需优先处理。

状态 任务 耗时 根因 修复建议 日志 重跑
其余 10 个必选任务通过 - - - - -

2.2 可选任务 — 29/32 通过

可选任务不阻塞合并,失败仅供参考。

状态 任务 耗时 日志 重跑
Run iluvatar Tests / run_iluvatar_cases 10m35s Job -
Check PR Template 12s Job -
CI_HPU 1h13m Job -
其余 29 个可选任务通过 - - -

3 失败详情(仅 required)

@zhoutianzi666 zhoutianzi666 changed the title commit [unitest] small change in test_deepgemm_precision.py May 15, 2026
PaddlePaddle-bot

This comment was marked as outdated.

PaddlePaddle-bot

This comment was marked as outdated.

@PaddlePaddle-bot
Copy link
Copy Markdown

🤖 Paddle-CI-Agent | ci_status_monitor | 2026-05-16 02:47:05

CI报告基于以下代码生成(30分钟更新一次):


1 任务总览

❌ 存在 1 个 Required 失败任务需要处理,其余 Required 任务已通过。

总执行(rerun次数) 总任务 ✅ 通过 ❌ 失败 ⏳ 运行中 ⏸️ 等待中 跳过
42(0) 42 38 3 0 1 0

2 任务状态汇总

2.1 Required任务 : 9/10 通过

必选任务阻塞合并,失败需优先处理。

状态 任务 耗时 根因 修复建议 日志 重跑
Pre Commit 44s PR问题:flake8 F841,test_flashmla_precision.py:60 未使用变量 a 删除或重命名 test_flashmla_precision.py:60 未使用变量 Job -
其余 9 个必选任务通过 - - - - -

2.2 可选任务 — 29/32 通过

可选任务不阻塞合并,失败仅供参考。

状态 任务 耗时 日志 重跑
Run iluvatar Tests / run_iluvatar_cases 34m40s Job -
Check PR Template 18s Job -
⏸️ CI_HPU - - -
其余 29 个可选任务通过 - - -

3 失败详情(仅 required)

Pre Commit — 代码规范(置信度: 高)

Pre Commit

  • 状态: ❌ 失败
  • 错误类型: 代码规范
  • 置信度: 高
  • 根因摘要: flake8 F841:test_flashmla_precision.py:60 存在未使用变量 a
  • 分析器: 通用分析(fallback)

根因详情:
Pre-commit 在 tests/operators/test_flashmla_precision.py 第60行检测到 flake8 F841 错误:局部变量 a 被赋值但从未被使用。该文件是本次 PR 的修改文件之一。其余代码风格检查(black、isort、ruff 等)均通过。

关键日志:

flake8...................................................................Failed
- hook id: flake8
- exit code: 1

tests/operators/test_flashmla_precision.py:60:21: F841 local variable 'a' is assigned to but never used

修复建议:

  1. 删除 tests/operators/test_flashmla_precision.py 第60行的未使用变量赋值语句,或将变量名改为 _ 以明确表示忽略
  2. 本地验证:pre-commit run --files tests/operators/test_flashmla_precision.py tests/operators/test_deepgemm_precision.py

修复建议摘要: 删除或重命名 test_flashmla_precision.py:60 未使用变量 a

关联变更: PR 修改文件:tests/operators/test_flashmla_precision.pytests/operators/test_deepgemm_precision.py

链接: 查看日志

PaddlePaddle-bot

This comment was marked as outdated.

@PaddlePaddle-bot
Copy link
Copy Markdown

🤖 Paddle-CI-Agent | ci_status_monitor | 2026-05-17 07:13:32

CI报告基于以下代码生成(30分钟更新一次):


1 任务总览

⚠️ 无必选(Required)检查配置,所有任务均为可选。已知可访问的任务中,3 个可选任务失败;另有 4 个 Workflow 因网络(TLS超时)无法获取状态,建议手动确认(含主测试任务 Run FastDeploy Unit Tests and Coverage / run_tests_with_coverage)。

总执行(rerun次数) 总任务 ✅ 通过 ❌ 失败 ⏳ 运行中 ⏸️ 等待中 跳过
9(0) 9 6 3 0 0 0

⚠️ 注意:以下 4 个 Workflow 因 TLS 握手超时无法获取 Job 状态,不计入上表统计:run_id: 25952268048, 25952268062, 25952267943, 25952267922。主测试任务 Run FastDeploy Unit Tests and Coverage / run_tests_with_coverage 可能位于其中,请手动确认 CI 详情


2 任务状态汇总

2.1 Required 任务:0/0 通过

当前未配置必选检查(Branch Protection Rules 中无 Required Status Checks),所有任务均为可选。

2.2 可选任务 — 6/9 通过

可选任务不阻塞合并,失败仅供参考。

状态 任务 耗时 失败原因 日志 重跑
CI_HPU 1h13m 环境问题:exit code 1 Job -
Check PR Template 12s PR模板:exit code 7 Job -
Run iluvatar Tests / run_iluvatar_cases 10m35s 环境问题:Pod unhealthy Job -
其余 6 个可选任务通过 - - - -

3 失败详情(仅 required)

无 required 失败任务。


可选任务失败说明

Run iluvatar Tests / run_iluvatar_cases

  • 错误类型:环境问题(基础设施)
  • 错误摘要:Pod iluvatar-gpu-2-nczzk-runner-dsqbn-workflow is unhealthy with phase status Pending
  • 处置建议:与 self-hosted runner 管理员联系,或等待 Pod 就绪后 rerun

Check PR Template

  • 错误类型:PR 格式检查
  • 错误摘要:Process completed with exit code 7(PR 描述不符合模板要求)
  • 处置建议:请按 PR 模板格式完善 PR 描述内容

CI_HPU

  • 错误类型:待进一步确认
  • 错误摘要:Process completed with exit code 1(运行时长 1h13m,疑为测试或环境问题)
  • 处置建议:查看完整日志确认根因,必要时 rerun

PaddlePaddle-bot

This comment was marked as outdated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants