Relationships
#4947 Flaky test: workspaceHub a busy child is not stopped until its runs end times out waiting for the hub to ask the busy child again
Opened by zack · 11/20/2026· Shipped 11/20/2026
integration/workspace_hub_test.ts:444, test workspaceHub: a busy child is not stopped until its runs end. It failed in a verify-build run (run a882b9c4-2db1-4d3b-96dd-b7ee95261b0b, commit 45e67ef47, a branch that does not touch this file) with: waitFor timed out after 10000ms waiting for the hub to ask the busy child again (workspace_hub_test.ts:449). Every other test in the suite passed. Possible cause, not confirmed: the test sets children[0].busy = true only after the first fetch has returned, while the hub runs with idleMs 20. If the hub's idle check asks the child before busy is set, it may stop the idle child, after which it never asks again, so busyAsks never reaches 2. Setting busy before the fetch, or otherwise making the busy state visible before the idle window can elapse, would remove the race.
Shipped
Click a lifecycle step above to view its details.
Sign in to post a ripple.