Skip to content

[ci] Fix scheduled failure reporting and monthly BSP builds - #11921

Open
CYFS3 wants to merge 2 commits into
RT-Thread:masterfrom
CYFS3:fix/daily-ci-reporting
Open

[ci] Fix scheduled failure reporting and monthly BSP builds#11921
CYFS3 wants to merge 2 commits into
RT-Thread:masterfrom
CYFS3:fix/daily-ci-reporting

Conversation

@CYFS3

@CYFS3 CYFS3 commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

拉取/合并请求描述：(PR description)

[

为什么提交这份PR (why to submit this PR)

每日 CI 的监控窗口只有 30 分钟，超时、取消、未找到运行等结果未被完整计入失败；监控脚本仍可能以成功退出，且失败后的报告步骤会被跳过。查找不到本轮运行时还会回退到历史记录，失败作业列表也可能因未分页而遗漏。

月度 BSP 构建仍使用已停用的 upload-artifact@v3，定时触发时缺少手动输入默认值，且 BSP 编译失败清单未反映到工作流退出状态。

你的解决方案是什么 (what is your solution)

  • 调整每日调度工作流及 trigger_workflows_direct.py、wait_for_workflows.py、monitor_workflows.py：传播触发、等待和监控失败状态；将单个工作流监控窗口延长至 120 分钟，设置请求超时；只查找开始时间之后 master 分支的 workflow_dispatch 运行，找不到时明确记录异常；分页读取失败作业。
  • 调整 generate_report.py 和报告步骤条件：统计全部非 success 结果，兼容缺少时间字段的异常记录并正确转换北京时间；前序检查失败后仍收集结果、生成报告并发布 Discussion。补充任务权限、限定上游仓库运行，并更新 github-script Action。
  • 修复月度 BSP 工作流：为定时触发提供 BSP 和工具链默认值；发现非空失败清单时返回失败；更新 upload-artifact 至 v4，并在构建失败后保留日志上传。
  • 已通过两个工作流的 actionlint 检查、Python 语法检查、12 项本地回归检查及真实 GitHub 运行数据回放；未进行整仓编译。

请提供验证的bsp和config (provide the config and bsp)

  • BSP:
  • .config:
  • action:

]

当前拉取/合并请求的状态 Intent for your PR

必须选择一项 Choose one (Mandatory):

  • 本拉取/合并请求是一个草稿版本 This PR is for a code-review and is intended to get feedback
  • 本拉取/合并请求是一个成熟版本 This PR is mature, and ready to be integrated into the repo

代码质量 Code Quality：

我在这个拉取/合并请求中已经考虑了 As part of this pull request, I've considered the following:

  • 已经仔细查看过代码改动的对比 Already check the difference between PR and old code
  • 代码风格正确，包括缩进空格，命名及其他风格 Style guide is adhered to, including spacing, naming and other styles
  • 没有垃圾代码，代码尽量精简，不包含#if 0代码，不包含已经被注释了的代码 All redundant code is removed and cleaned up
  • 所有变更均有原因及合理的，并且不会影响到其他软件组件代码或BSP All modifications are justified and not affect other components or BSP
  • 对难懂代码均提供对应的注释 I've commented appropriately where code is tricky
  • 代码是高质量的 Code in this PR is of high quality
  • 已经使用clang-format 源码格式化工具确保格式符合RT-Thread代码规范 This PR has been formatted with clang-format and complies with RT-Thread code specification
  • 如果是新增bsp, 已经添加ci检查到.github/ALL_BSP_COMPILE.json 详细请参考链接BSP自查

@github-actions github-actions Bot added action github action yml imporve tools labels Oct 23, 2026
@github-actions

github-actions Bot commented Oct 23, 2026

Copy link
Copy Markdown

👋 感谢您对 RT-Thread 的贡献！Thank you for your contribution to RT-Thread!

为确保代码符合 RT-Thread 的编码规范，请在你的仓库中执行以下步骤运行代码格式化工作流（如果格式化CI运行失败）。
To ensure your code complies with RT-Thread's coding style, please run the code formatting workflow by following the steps below (If the formatting of CI fails to run).

🛠 操作步骤 | Steps

  1. 前往 Actions 页面 | Go to the Actions page
    点击进入工作流 → | Click to open workflow →

  2. 点击 Run workflow | Click Run workflow

  • Use workflow from 保持默认分支（通常为 master）
    Keep the default branch (usually master) in Use workflow from
  • 在 branch 输入框填写 PR 分支 fix/daily-ci-reporting
    Enter PR branch fix/daily-ci-reporting in the branch field
  • 设置需排除的文件/目录（目录请以"/"结尾）
    Set files/directories to exclude (directories should end with "/")
  1. 等待工作流完成 | Wait for the workflow to complete
    格式化后的代码将作为独立提交推送至你的分支。
    The formatting changes will be pushed to your branch as a separate commit.

完成后，提交将自动更新至 fix/daily-ci-reporting 分支，关联的 Pull Request 也会同步更新。
Once completed, commits will be pushed to the fix/daily-ci-reporting branch automatically, and the related Pull Request will be updated.

如有问题欢迎联系我们，再次感谢您的贡献！💐
If you have any questions, feel free to reach out. Thanks again for your contribution!

@github-actions

github-actions Bot commented Oct 23, 2026 •
edited
Loading

Copy link
Copy Markdown

📌 Code Review Assignment

🏷️ Tag: workflow

Reviewers: @Rbb666 @kurisaW @supperthomas

Changed Files (Click to expand)
  • .github/workflows/manual_bsp_build.yml
  • .github/workflows/scheduled-ci-trigger.yml

📊 Current Review Status (Last Updated: 2026-10-24 19:08 CST)

📝 Review Instructions

  1. 维护者可以通过单击此处来刷新审查状态: 🔄 刷新状态
    Maintainers can refresh the review status by clicking here: 🔄 Refresh Status

  2. 确认审核通过后评论 LGTM/lgtm
    Comment LGTM/lgtm after confirming approval

  3. PR合并前需至少一位维护者确认
    PR must be confirmed by at least one maintainer before merging

ℹ️ 刷新CI状态操作需要具备仓库写入权限。
ℹ️ Refresh CI status operation requires repository Write permission.

@github-actions

github-actions Bot commented Oct 23, 2026 •
edited
Loading

Copy link
Copy Markdown

MemBrowse Memory Report · Explore what changed →

No memory changes detected for:

Catch memory regressions in CI with MemBrowse. Free for open source.

cms19859230182-lang
cms19859230182-lang reviewed Oct 24, 2026
View reviewed changes
Comment thread tools/ci/scheduled-ci-trigger/monitor_workflows.py Outdated
Comment on lines 217 to 220
results = monitor_workflows(github_token, repo, workflows, start_time)

with open("monitoring_results.json", "w") as f:
with open("monitoring_results.json", "w", encoding="utf-8") as f:
json.dump(results, f, indent=2)

@cms19859230182-lang cms19859230182-lang Oct 24, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

结果文件要等全部监控完才写（2×120min 贴着 270min 超时），中途被杀整份报告都丢；建议每监控完一个就落盘。

Comment thread tools/ci/scheduled-ci-trigger/generate_report.py
return

failed_workflows = [r for r in results if r.get('conclusion') == 'failure']
failed_workflows = [r for r in results if r.get('conclusion') != 'success']

@cms19859230182-lang cms19859230182-lang Oct 24, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

非 success 已计入，但只对 failure 拉 jobs，cancelled 等几乎没详情。

This branch has not been deployed

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

Reviewers

@supperthomas supperthomas Awaiting requested review from supperthomas supperthomas is a code owner
@kurisaW kurisaW Awaiting requested review from kurisaW kurisaW is a code owner
1 more reviewer
@cms19859230182-lang cms19859230182-lang cms19859230182-lang left review comments
Reviewers whose approvals may not affect merge requirements

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

action github action yml imporve tools

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@CYFS3 @cms19859230182-lang