neuwirth
/
pmacs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(ci-reds): U16's third occurrence, and the first on `main` 

The post-merge gate of the docs-only absorption commit redded at
`07-sweep` with U16's exact signature. Same selector, same panic site,
both required fragments.

It is the first occurrence on `main`, which removes the last attribution
question this row could have had --- the first two were on a branch
whose diff touched nothing under `src/packages/`, and this one has no
observing branch at all.

Three occurrences in about eleven hours, against eight consecutive green
`--lib` runs earlier the same morning. That is the closest this row has
to a rate and it is still not a measurement, because nobody has counted
runs and failures over a fixed window. Isolated reruns green three
times, which per the rerun rule establishes intermittence only.

The structural fix belongs to `file_io`: a version-suffixed child
inherits a cwd that a `TempDir` then deletes, and no care inside the
mutating test can close a process-wide window.
This commit is contained in:
Levi Neuwirth 2026-08-31 21:02:45 +02:00
parent 90238fbe51
commit 0ec13b3953
No known key found for this signature in database
2 changed files with 29 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/active-work.md
View File

@ -439,8 +439,15 @@ U17, U18 and U19. *(This heading said "four" while listing more; corrected.)*
the failure returned within the day. The child-inheritance chain
stays a candidate; this occurrence demonstrates it no more than the
first did. **It then passed in all three stages of the next gate
run** — two reds and many greens **all on 2026-08-31**, intermittent at
a rate nothing has measured.
run** — reds and greens **all on 2026-08-31**, intermittent at a rate
nothing has measured. **A THIRD occurrence followed on `main`**
(log `20260831T185716Z-4031066`, the post-merge gate of a docs-only
commit), which removes the last attribution question: there is no
observing branch to suspect. Three in about eleven hours against
eight consecutive green `--lib` runs the same morning — the closest
this row has to a rate, and still not a measurement.
**The structural fix in `file_io` is now the thing worth doing**, and
it is not this lane's.
- **U19, new** — `terminal_bell_baseline_…` timed out on a **5-second**
poll, in the same run as U16's second. The evidence is that **no bell
was observed within five seconds** — not that one never came, and not

22
docs/ci-red-signatures.md
View File

@ -1521,7 +1521,7 @@ which is why it was worth recording before it had reproduced.
| **selector** | `--lib packages::fetcher::tests::cache_survives_across_fetcher_instances` |
| **job / flavor** | local (Linux), `scripts/gate` step `07-sweep` (`cargo test --workspace --no-fail-fast`) |
| **required fragments** | `Unable to read current working directory: No such file or directory` + `remote did not send all necessary objects` |
| **status** | **SECOND OCCURRENCE 2026-08-31 — it reproduced, in the same step, with the same fragments** |
| **status** | **THREE OCCURRENCES, all 2026-08-31, within about eleven hours** — and the third is **on `main`** |
| **what IS established** | the fragments, captured from the durable stage log at `src/packages/fetcher.rs:929`. `1989 passed; 1 failed`. The test spawns `git` against a `file://` remote in a temp dir |
| **what is NOT** | that the mechanism below is what happened. It is a candidate with a citation, not a demonstrated chain |
| **the observing tree** | the lane's docs-only commit. It touches `src/packages/` not at all |
@ -1588,11 +1588,29 @@ demonstrates the chain either.
**And it passed again immediately after**, in all three stages of the
next gate run — `03-lib`, `04-lib-crdt` and the same `07-sweep` context
— at `ea786a2`, log `20260831T174716Z-3535694`. Two reds and many greens
— at `ea786a2`, log `20260831T174716Z-3535694`. Reds and greens
**all on 2026-08-31**: **intermittent**, at a rate nothing here has
measured. *(An earlier version said "across two days"; every run cited
by this row is the same day, as the sentences above it already said.)*
**THIRD OCCURRENCE, 2026-08-31, log `20260831T185716Z-4031066`, step
`07-sweep` — and this one is ON `main`.** Same selector, same panic site
`fetcher.rs:929`, both required fragments, `1989 passed; 1 failed`. The
run was the post-merge gate of `90238fb`, a **documentation-only**
commit on `main` after #246 landed.
**That removes the last attribution question this row could have had.**
The first two occurrences were on a branch whose diff touched no file
under `src/packages/`; this one is on `main`, where there is no
observing branch to suspect at all — the same distinction U17 draws.
Three occurrences in about eleven hours, against eight consecutive
green `--lib` runs earlier the same day, is also the closest this row
has to a rate, and it is still not a measurement: nobody has counted
runs and failures over a fixed window.
**Isolated reruns after it: green three times** (`1 passed` each).
Intermittence only, as before.
**Not folded into U14 or U15.** Different selector, different fragments,
different step, and a different kind of failure: those are wall-clock
budgets under load, this is a race over process-global state. U14's