Skip to content

[CI] Skip CI for non-runtime directories#7870

Open
EmmonsCurse wants to merge 3 commits into
PaddlePaddle:developfrom
EmmonsCurse:ci_optimize_dev_0520
Open

[CI] Skip CI for non-runtime directories#7870
EmmonsCurse wants to merge 3 commits into
PaddlePaddle:developfrom
EmmonsCurse:ci_optimize_dev_0520

Conversation

@EmmonsCurse

@EmmonsCurse EmmonsCurse commented May 20, 2026

Copy link
Copy Markdown
Collaborator

Motivation

Changes under documentation, tooling, benchmark, and auxiliary configuration directories do not affect runtime behavior directly. Running full CI for these modifications increases unnecessary resource usage and slows down development workflow.

Modifications

  • Added CI skip rules for changes under:
    • .claude/
    • benchmarks/
    • docs/
    • dockerfiles/
    • examples/
    • tools/
  • Reduced unnecessary CI triggering for non-runtime related changes.

Usage or Command

N/A

Accuracy Tests

N/A

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.

@EmmonsCurse

Copy link
Copy Markdown
Collaborator Author

/skip-ci ci_iluvatar
/skip-ci ci_hpu
/skip-ci build_xpu
/skip-ci build_gpu

@paddle-bot

paddle-bot Bot commented May 20, 2026

Copy link
Copy Markdown

Thanks for your contribution!

PaddlePaddle-bot

This comment was marked as outdated.

PaddlePaddle-bot

This comment was marked as outdated.

@PaddlePaddle-bot

PaddlePaddle-bot commented May 20, 2026

Copy link
Copy Markdown

🤖 Paddle-CI-Agent | ci_status_monitor | 2026-05-28 12:24:41

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


1 任务总览

Required 任务当前无失败、无运行中、无等待中;本 PR 属于 CI skip 规则调整,部分测试任务按跳过逻辑被跳过。建议重点关注 Optional 失败任务是否需要人工确认;Required 侧暂无阻塞。

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

2 任务状态汇总

2.1 Required任务 : 2/10 通过

必选任务阻塞合并,失败需优先处理。当前 Required 无失败/运行中/等待中;其余 Required 任务因 skip 规则跳过。

状态 任务 耗时 根因 修复建议 日志 重跑
其余 2 个必选任务通过 - - - - -
⏭️ 8 个必选任务跳过 - CI skip 规则触发 无需处理 - -

2.2 可选任务 — 22/32 通过

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

状态 任务 耗时 日志 重跑
Trigger Jenkins for PR 22s Job -
其余 22 个可选任务通过 - - -
⏭️ 9 个可选任务跳过 - - -

3 失败详情(仅 required)

无 required 失败任务。本次未调用深度失败分析;Optional 失败任务不阻塞合并,仅在上方可选任务区展示。

PaddlePaddle-bot

This comment was marked as outdated.

PaddlePaddle-bot

This comment was marked as outdated.

PaddlePaddle-bot

This comment was marked as outdated.

@EmmonsCurse

Copy link
Copy Markdown
Collaborator Author

/skip-ci all

PaddlePaddle-bot

This comment was marked as outdated.

@EmmonsCurse EmmonsCurse changed the title [CI] Skip CI for non-runtime directories and add unittest Claude skill [CI] Skip CI for non-runtime directories May 28, 2026

@PaddlePaddle-bot PaddlePaddle-bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🤖 Paddle-CI-Agent | pr_review | 2026-05-28 11:49:58

📋 Review 摘要

PR 概述:为 CI 跳过检查规则新增非运行时目录白名单(.claude/benchmarks/docs/dockerfiles/examples/tools/),减少不必要的 CI 触发。
变更范围.github/workflows/check-bypass.yml
影响面 Tag[CI]

问题

未发现阻塞性问题。PR 规范问题在下面章节报,不要在这里重复。

历史 Findings 修复情况

Finding 问题 状态
F1 Checklist "Add unit tests" 未勾选且未说明原因 ⚠️ 仍存在

📝 PR 规范检查

Checklist 中 "Add unit tests" 项未勾选且未在 PR 中说明原因,模板要求 "Please write the reason in this PR if no unit tests"。建议在描述中补充说明(如:本 PR 仅修改 CI 配置,无需添加单元测试)。

标题建议:标题合规,无需修改。

PR 描述建议(点击展开,可直接复制)
## Motivation
Changes under documentation, tooling, benchmark, and auxiliary configuration directories do not affect runtime behavior directly. Running full CI for these modifications increases unnecessary resource usage and slows down development workflow.

## Modifications
- Added CI skip rules in `.github/workflows/check-bypass.yml` for changes under:
  - `.claude/`
  - `benchmarks/`
  - `docs/`
  - `dockerfiles/`
  - `examples/`
  - `tools/`
- Reduced unnecessary CI triggering for non-runtime related changes.

## Usage or Command
N/A

## Accuracy Tests
N/A

## Checklist

- [x] 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.
- [x] Format your code, run `pre-commit` before commit.
- [ ] Add unit tests. Please write the reason in this PR if no unit tests.
  - 本 PR 仅修改 CI 配置文件(`.github/workflows/check-bypass.yml`),无需添加单元测试。
- [ ] 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.

总体评价

变更逻辑清晰,Bash 正则语法正确,continue 跳过白名单目录的实现符合预期,不影响已有 .md/.yaml/.go 判断路径。PR 规范问题不阻塞合入。

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.

2 participants