Repository navigation
ci_preflight: per-stage startedAt and seconds in preflight-summary.json (CR-143) - #402
Merged
Merged
Conversation
![github-code-quality[bot]](https://avatars.githubusercontent.com/u/9919?s=60&v=4){kind=small}
Comment on lines
+775
to
+777
| 'import json, pathlib; ' | ||
| 'p = pathlib.Path("logs/preflight-summary.json"); ' | ||
| 'pathlib.Path("logs/mid-run.json").write_text(p.read_text())' |
Resolve CHANGELOG.md: this branch's preflight-timings line joins the 1.6.1 — Unreleased section #401 opened, instead of a separate Unreleased heading, since it ships in the same release. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
luisleo526
added a commit
that referenced
this pull request
Oct 17, 2026
* docs: the 1.6.1-rc.1 release candidate notes Prepare the 1.6.1-rc.1 changelog entry dated 2026-10-17, carrying forward the reviewed 1.6.1 — Unreleased section (b148979, c818585) and naming all pull requests merged since v1.6.0 (#398, #400, #401, #402). Update the two CHANGELOG section anchor links in README.md and docs/pages/public-contract.md introduced by b148979 from #161--unreleased to #161-rc1--2026-10-17 while keeping the current final release and pair lines on 1.6.0. * docs: drop the hpo-candidate pairing line from the 1.6.1-rc.1 entry (review of #403) No pineforge-hpo release candidate exists yet and the reviewed 1.6.1 entry did not claim one. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> --------- Co-authored-by: HaoLiangWen <[email protected]> Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
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.
CR-143.
scripts/ci_preflight.pynow recordsstartedAt(UTC ISO-8601) andseconds(monotonic duration, 3 decimals) for every stage inpreflight-summary.json, plus both values for the run as a whole. A stage that is still running hasseconds: null. The summary is still rewritten at every stage start and end. So when preflight times out, the summary shows which stage was running and how long it had been going.Today a CLOUD preflight timed out four times at 1,800 s, each time in stage 23 of 51 (
verifier-tests). The summary carried no timing, so nobody could tell which stage was slow.Only keys are added; every existing key and value is unchanged. Readers checked: the tests in scripts/test_ci_preflight.py;
lab remote'spreflight-summarykeyline (pineforge-workflow campaign/src/remote/keylines.mjs:145), which reads status, exitCode and stages only; ci_verify.py, which does not read this file. Red test first (971ee20), change second (a2bb972).🤖 Generated with Claude Code