docs(08-05): record fetchguard flake resolution in deferred items
This commit is contained in:
@@ -60,3 +60,9 @@ run; passes on every isolated run (`-count=5`) and every package-level run
|
|||||||
(`-count=3`). Last touched in Phase 6 (`e50e2dd`); no Phase 8 plan modifies
|
(`-count=3`). Last touched in Phase 6 (`e50e2dd`); no Phase 8 plan modifies
|
||||||
`fetchguard`. Timing-sensitive streaming assertion under load. Not a Phase 8
|
`fetchguard`. Timing-sensitive streaming assertion under load. Not a Phase 8
|
||||||
regression; left for a later hardening pass.
|
regression; left for a later hardening pass.
|
||||||
|
|
||||||
|
**Resolution (orchestrator, after 08-05):** the flake tripped the post-wave
|
||||||
|
gate on two of three full runs, so it was fixed in `summercms.go` commit
|
||||||
|
`test(fetchguard): widen streaming-cap ceiling to stop flake under parallel
|
||||||
|
runs`. The ceiling moved from 64 KiB to 1 MiB; the assertion still proves the
|
||||||
|
client does not buffer an unbounded body (the handler would reach 8 MiB).
|
||||||
|
|||||||
Reference in New Issue
Block a user