File item 439: the stalled-fetch test fails on a loaded runner
CI / tests (pull_request) Successful in 3m43s

This commit was merged in pull request #620.
This commit is contained in:
2026-11-18 22:38:21 +01:00
parent b976fa862a
commit 291d97a8f9
+9 -1
View File
@@ -6,12 +6,13 @@
`Bar = 0.1`
`Next ID = 439`
`Next ID = 440`
## Items
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 439 | 0.12.0 | | | **Make the stalled-fetch test in chunk-preflight pass on a loaded CI runner.** | 1 | 1 | 1 | 1 | 2 | code health by 2 | 3.5 |
| 410 | 0.12.0 | | | **Run `do-epic <EPIC-KEY>`: one tmux session per epic, a window per chunk, up to the epic's cap of running chunks and each repo's `parallel-chunks`, and never in a repo a loop-claude is running chunks in.** | 3 | 2 | 3 | 6 | 6 | 1 by 5 | 0.8 |
| 416 | 0.12.0 | 410 | | **Finish an epic's repo item with a bullet under its repo's `CHANGELOG.md` → `## Unreleased`, or with none where the repo's plan is in Jira.** | 1 | 1 | 1 | 1 | 2 | 1 by 5 | 2.1 |
| 413 | 0.12.0 | 410 | | **File a finding about an epic goal in the epic and one about a repo goal by that repo's rules, ask the human where unsure which, and give the judge the epic's records beside the repo's.** | 3 | 2 | 3 | 6 | 4 | 1 by 5 | 1.6 |
@@ -76,6 +77,13 @@
## Details
### 439. Make the stalled-fetch test in chunk-preflight pass on a loaded CI runner.
CI run 6716 on PR #617 failed once, in `bin/chunk_preflight/test_chunk_preflight.py::ChunkPreflightTool::test_reads_origin_as_last_fetched_where_the_fetch_stalls_and_still_states_the_other_facts`, and passed on a rerun of the same commit. The test sets `CHUNK_PREFLIGHT_TIMEOUT=1` for the stalled fetch, and a loaded runner takes longer than one second for `reading-cost`, so `reading-cost exited 0` is missing from the output. A rerun costs about five minutes of CI per occurrence.
Touches:
- `bin/chunk_preflight/test_chunk_preflight.py`: `test_reads_origin_as_last_fetched_where_the_fetch_stalls_and_still_states_the_other_facts`
### 410. Run `do-epic <EPIC-KEY>`: one tmux session per epic, a window per chunk, up to the epic's cap of running chunks and each repo's `parallel-chunks`, and never in a repo a loop-claude is running chunks in.
The lock that keeps do-epic and loop-claude apart is the per-project `starting` flock, shared by both (`docs/decisions.md` → `do-epic: drives one Jira epic …`). Each chunk routes on its repo's model and ladder, a no-repo chunk on the machine setting's model. `loop/chunk_windows.py` `start_chunks` is a place the seats found hard: make it easier to read where it changes. Where a do-epic cycle's worker, judge or human reads the driver's name, they read do-epic, never loop-claude: item 401 left `agent_cycle`'s own text naming loop-claude, since whether the markers that code matches (`TYPED_HERE`, `TRANSCRIPT_HEADING`) vary by driver depends on what do-epic calls itself and where it archives its cycles. The worker's prompt and the judge's rules share the phrase a worker asks for a higher rung with, so both take it from one place.