Skip to content

test: give the stall-watch progress test room on busy CI runners - #768

Merged
KnifeLemon merged 1 commit into
mainfrom
test/stall-watch-margins
Oct 29, 2026
Merged

KnifeLemon merged 1 commit into
mainfrom
test/stall-watch-margins

Conversation

@KnifeLemon

Copy link
Copy Markdown
Owner

StallWatchTests.A_program_that_keeps_reporting_runs_well_past_the_stall_limit touched the watch every 50 ms against a 300 ms limit. On loaded runners one 50 ms wait sometimes took longer than 300 ms, and the test failed on unrelated PRs (#759, #765, #766, #745).

The limit is now 1 s and the fake program reports for 3 s, still three times the limit. The test takes 2 s longer.

🤖 Generated with Claude Code

A_program_that_keeps_reporting_runs_well_past_the_stall_limit touched every
50 ms against a 300 ms limit and failed several times today when a loaded
runner delayed one wait past 300 ms (#759, #765, #766). The limit is now 1 s
and the fake program reports for 3 s, still three times the limit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@KnifeLemon
KnifeLemon merged commit 314e843 into main Oct 29, 2026
9 checks passed
KnifeLemon added a commit to skyhilam/Filee that referenced this pull request Oct 30, 2026
A_program_that_keeps_reporting_runs_well_past_the_stall_limit still failed
on CI after KnifeLemon#768 (KnifeLemon#790's run): its fake output was a Task.Delay loop, which
waits for the thread pool, and the other test classes running in parallel
can hold that up for over a second, so the watch saw a stall. The output
now comes from a dedicated thread, like the real output reader, and the
test's continuation runs asynchronously so it never joins its own thread.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
adnan-bhaldar pushed a commit to adnan-bhaldar/Filee that referenced this pull request Oct 30, 2026
A_program_that_keeps_reporting_runs_well_past_the_stall_limit still failed
on CI after KnifeLemon#768 (KnifeLemon#790's run): its fake output was a Task.Delay loop, which
waits for the thread pool, and the other test classes running in parallel
can hold that up for over a second, so the watch saw a stall. The output
now comes from a dedicated thread, like the real output reader, and the
test's continuation runs asynchronously so it never joins its own thread.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant