A Signal's new hits test fails in the full browser suite, passes alone #415
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
tests/ui/app.spec.ts:38, 'a Signal's new hits reach its open page and its count without a reload', failed once in a full npx playwright test run on 2026-11-07 (toBeVisible timed out) and passed when run alone straight after. Something earlier in the suite leaves state it depends on, or it races the judge.
Not only a flaky test: subscribing to a feed the server already had never woke the Signals judge, so its recent items reached the new subscriber's Signals only at the next idle pass, up to five minutes later. The test hit it whenever an earlier test had subscribed to the same fixture feed and left. Fixed in
5a8a7fb: scan_soon, which every subscribe from the API goes through, wakes the judge. The test now passes in suite order in about a second. Deployed.