Repository navigation
Conversation
|
The targeted janitor regressions and static checks pass. The only red job is Ubuntu / Node 24 / shard 3: tests/seq-interval-lane.test.ts:180 read zero persisted blocks after the tool reported one applied block (2,879 passed, 1 failed, 18 skipped). Failure log: https://github.com/ranxianglei/billion-context/actions/runs/42995321477/job/130438108992 . The test uses a fixed 60 ms sleep before reading SQLite, while persistence runs on a debounced asynchronous write chain; the log does not establish the exact failing interleaving. This PR does not change that test or persistence path. The same test passed on the current #6188 head in the same Ubuntu/Node24 shard: https://github.com/ranxianglei/billion-context/actions/runs/42997474540/job/130445327525 . Could the failed shard be rerun on unchanged head d992d5d? |
|
Landed via batch PR #6439 (merged) — closing as superseded. |
(ai: vllm-qwen/qwen3.8-27b) Live state re-verified first — no active work: PR #6221 is CLOSED (not merged). Per the lane rules I re-verified the live state before touching anything:
So there is no active PR to fix and no branch I'm permitted to push to. No changes were pushed. For the record — I did diagnose the red check. It is a pre-existing test flake, unrelated to this PR's janitor changes: Stopping — nothing further to do on a closed PR. 结构化八问(中文结论)
判定:无可执行工作(PR 已关闭),收工。 |
(ai: vllm-qwen/qwen3.8-27b) Understood — verified: batch PR #6439 ("land 50 open Afloat16 fixes") merged at 2026-11-12T14:01:25Z, carrying the janitor change; #6221 was closed as superseded ~9 min later (14:10:18Z). That matches the stale-wake state I reported (PR closed, no active work, no push access to the fork). For the record: the red |
(ai: vllm-qwen/qwen3.8-27b) Re-verified live — this is another stale wake: PR #6221 is still CLOSED (not merged).
No action taken — nothing to rebase on a closed, superseded PR. 结构化八问(中文结论)
判定:无可执行工作(PR 已关闭且被 #6439 取代),收工。 |
Related to the CI consolidation issue #4599.
Problem
The janitor tests every PR head branch in the upstream repository. A branch owned by a contributor fork is therefore reported as deleted even while it still exists, and its active CI run is cancelled. Any failed branch API request is also treated as deletion.
This is happening in production: janitor run https://github.com/ranxianglei/billion-context/actions/runs/42987251353/job/130411257674 cancelled multiple live fork runs with the reason
head branch ... deleted. For example, run https://github.com/ranxianglei/billion-context/actions/runs/42985136714 belongs toAfloat16/billion-context, branch2026-11-11_responses-string-recovery, but the lookup usedranxianglei/billion-context. The janitor reported queue depth 8 queued / 3 in progress, so this cancellation was not its starvation rule.Change
Carry
head_repository.full_namealongside each run, URL-encode the branch component, and check that branch in its owning repository. Treat only a branch HTTP 404 from an otherwise accessible repository as a confirmed deletion. Missing head metadata, inaccessible repositories, rate limits and server errors no longer masquerade as deleted branches. Existing age cleanup, dry-run behavior and scheduled-master protection remain in effect.Validation
Head:
d992d5dc09eca67596266b7d9e0b818894341716, based on masterdc041dd1ab1a014efa352ba47a6f31fc47f55284.npm run typecheck,npm run buildandgit diff --checkpass.scripts/live-files.mjs. It runs on Linux, matching the workflow runner; it skips other platforms because the script uses GNU date.Command:
node --test tests/ci-janitor-fork-heads.test.ts(Node.js 24.22.1 on Linux). The test makes no network requests and cancels no real run.This fixes the cleanup classification; it does not claim that previously cancelled upstream jobs have been rerun.