Development record
TestEveryStreamFailureIsRefusedWithoutTheKey/a_stream_that_never_ends failed on the CI ubuntu runner with 'the call had not returned after 30s' for a config-only change (PR #859, run 37710101909); it passed on rerun, so its fixed wall-clock wait is flaky under load.
issueresolvedminoriss-2610080243367274
TestEveryStreamFailureIsRefusedWithoutTheKey/a_stream_that_never_ends failed on the CI ubuntu runner with 'the call had not returned after 30s' for a config-only change (PR #859, run 37710101909); it passed on rerun, so its fixed wall-clock wait is flaky under load.
Grounds
- pursued: the case returns within a wait derived from the adapter's own deadline whatever the runner's throughput; a CI run failing it with 'the call had not returned after' a wait derived from the cap would show it wrong
Frontmatter
| id | iss-2610080243367274 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610080243367274-testeverystreamfailureisrefusedwithoutth.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610102020447522Two internal/core/interview tests fail under machine load with 'WaitDelay expired' (a different test on each run), on 2026-10-10 in two consecutive make preflight runs of a drain lane at load averages of 31 to 57 on 16 cores; the package passes when run alone and under the race lane. The tests' subprocess wait is a fixed wall-clock budget that a loaded runner overruns, the same shape as the openaiapi stream test fixed for iss-2610080243367274.