Skip to content

test(the-framework): give the re-home polls a budget a CI runner can meet#1154

Merged
suleimansh merged 1 commit into
mainfrom
test/1153-rehome-poll-budget
Jul 25, 2026
Merged

test(the-framework): give the re-home polls a budget a CI runner can meet#1154
suleimansh merged 1 commit into
mainfrom
test/1153-rehome-poll-budget

Conversation

@suleimansh

Copy link
Copy Markdown
Member

Closes #1153.

The #1122 re-home test fails on CI at 6578ms against a 6s ceiling — 300 attempts 20ms apart, waiting on an events tail, a project resolve, a git worktree add and a spawn. It timed out rather than observed a wrong result. Seen on main at 47049ab (run 30136805342) and twice on an unrelated branch (run 30155239647, first attempt and re-run), so it is not tied to any one change.

One shared POLL_ATTEMPTS (1500 × 20ms = 30s) for the three polls in that file. They all return the moment what they wait for lands, so the larger cap costs nothing on a fast machine and only shows up on a real failure.

1277 tests green locally. Test-only, no changeset.

…meet

The #1122 re-home test failed on CI at 6578ms against a 6s ceiling: 300
attempts 20ms apart, waiting on an events tail, a project resolve, a git
worktree add and a spawn. It timed out rather than observed a wrong result,
and it took main red with it.

The loops return the moment what they wait for lands, so a 30s ceiling costs
nothing when things are fast and only shows up on a real failure.

Closes #1153
@suleimansh suleimansh added bug Something isn't working priority: low Nice to have / latent the-framework ♻️ labels Jul 25, 2026
@suleimansh suleimansh self-assigned this Jul 25, 2026
@suleimansh
suleimansh marked this pull request as ready for review July 25, 2026 11:19
@suleimansh
suleimansh merged commit 0c3a5a9 into main Jul 25, 2026
1 check passed
@suleimansh
suleimansh deleted the test/1153-rehome-poll-budget branch July 25, 2026 11:19
suleimansh added a commit that referenced this pull request Jul 25, 2026
… timeout (#1160)

The 30s ceiling from #1154 was too generous in the wrong direction: a single
re-home test runs two of these polls, so two slow waits alone reached the
suite's 60s per-test timeout and a slow test became a file timeout.

15s each still clears the 6.5s the failing CI run needed, and leaves the real
git work between them inside the cap.

Follows #1153
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working priority: low Nice to have / latent the-framework ♻️

Projects

None yet

Development

Successfully merging this pull request may close these issues.

test: the #1122 re-home test times out on CI at its 6s poll budget

1 participant