Repository navigation
Commit 34aab3c
committed
ci: run the tmpdir model tests off the Coverage lane
check:tmpdir-leaks:test proves the TMPDIR lifecycle by spawning a real nested
`vitest run`. Sitting it in the Coverage job — seconds before the full
instrumented suite — is a contention risk for no benefit, so it moves to the
Layering Guard job.
The Coverage lane already loses runs to `[vitest-pool]: Worker forks emitted
error` when a fork is slow to terminate; main hit exactly that at 18291ba
(scripts/fuzz/corpus-replay.test.ts, 708/709 files passed, zero failed tests)
before this gate existed. That flake is not caused by this branch, but starting
a second Vitest right before the big one can only make it likelier.
The leak detector itself (`check:tmpdir-leaks`) stays in Coverage, where it has
to run: it reads what the suite left behind, and it spawns nothing.
Ownership is proven per unit of work, so the manifest is satisfied by any lane
running these tests — moving the step keeps the gate wired.
Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01SkS4S8XXrfkJ8TD1VBKkvJ1 parent c6e42f4 commit 34aab3c
1 file changed
Lines changed: 14 additions & 7 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
116 | 116 | | |
117 | 117 | | |
118 | 118 | | |
| 119 | + | |
| 120 | + | |
| 121 | + | |
| 122 | + | |
| 123 | + | |
| 124 | + | |
| 125 | + | |
| 126 | + | |
| 127 | + | |
| 128 | + | |
| 129 | + | |
| 130 | + | |
| 131 | + | |
| 132 | + | |
119 | 133 | | |
120 | 134 | | |
121 | 135 | | |
| |||
266 | 280 | | |
267 | 281 | | |
268 | 282 | | |
269 | | - | |
270 | | - | |
271 | | - | |
272 | | - | |
273 | | - | |
274 | | - | |
275 | | - | |
276 | 283 | | |
277 | 284 | | |
278 | 285 | | |
| |||
0 commit comments