Repository navigation
[PR] ci: cancel superseded master-build artifact runs - #3156
Open
ranxianglei wants to merge 5 commits into
Open
ranxianglei wants to merge 5 commits into
ranxianglei wants to merge 5 commits into
Conversation
Every e2e lane and the main CI have per-ref concurrency with cancel-in-progress since #2637, but master-build.yml has no concurrency block at all — two rapid merges stack two artifact builds and both hold a runner slot to completion even though only the newest commit's artifact is ever consumed. Same slot-hygiene pattern as the rest: group by ref, cancel the superseded run. Deliberately NOT touched: - release*.yml — release runs must never cancel each other (release-bugfix/release-manual already pin cancel-in-progress: false) - ci.yml path filters — #3085 explicitly reverted hot-file gating; full-matrix-per-PR is policy
Contributor
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.6202-pr.3156.5aa214dThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr3156.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Owner
Author
(ai: vllm-qwen/qwen3.8-27b) PR 已核对完毕(分支 结构化八问
独立核查记录(不引用 issue 侧结论,自己重做的):
|
Owner
Author
(ai: vllm-qwen/qwen3.8-27b) CI 收尾更新:39 个 check run 全部完成,38 绿、1 红——唯一失败是
处置建议:对失败的 job 点一次 Re-run failed jobs 即可,预期转绿后合并;flake 本身的修复归 #3152,不在本 PR 范围内。其余八问结论维持上一条回复不变——可合。 |
added 3 commits
October 26, 2026 14:17
master window commits 293ae65/de5e03659 bumped kernel/package.json to 0.0.165 without regenerating the lockfiles; lock-sync re-resolution then rewrites the stale recorded versions (root 0.0.163, kernel 0.0.164) and fails. Pure recorded-version sync via npm install --package-lock-only; no dependency or semantic change.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Queue-slot hygiene follow-up to #2637.
What: master-build.yml was the only always-on master workflow with no concurrency block — two rapid merges stack two artifact builds, and both hold a runner slot to completion even though only the newest commit's artifact is ever consumed. Adds the same per-ref group + cancel-in-progress: true every e2e lane and the main CI already use.
Audit note: I initially read 8 e2e workflows as missing cancel-in-progress — false positive from a too-narrow grep window (the flag sits two comment lines below the group). They were already correct and are untouched.
Deliberately NOT touched: