Skip to content

Give the fork's identity tests the suite's connection timeout - #83

Merged
MiguelsPizza merged 1 commit into
mainfrom
alex/fix-identity-test-timeouts
Sep 23, 2026
Merged

MiguelsPizza merged 1 commit into
mainfrom
alex/fix-identity-test-timeouts

Conversation

@MiguelsPizza

Copy link
Copy Markdown
Contributor

CI on main failed right after the 0.9.0 release merge (#78). This fixes the flaky test. The npm publish itself succeeded.

Cause. "starts identity comparison over when the requested address changes" is one of two useAgent identity tests the fork added in db417b5. Both wait for a fresh agent's identity callback with vi.waitFor's default one-second window. On a cold runner the first connection to a new Durable Object took longer than that, so the wait ended with zero calls recorded. Every other connection wait in rpc-robustness.test.tsx already passes a ten-second timeout.

Fix. Give the four waits in those two tests the same { timeout: 10000 } as the rest of the file. Test-only, so no changeset and no fork-diff row change.

Check. The file passes 16 of 16 locally in Chromium. The failure is timing-only, so I did not build a deterministic reproduction.

🤖 Generated with Claude Code

The two useAgent identity tests the fork added in db417b5 wait for a
fresh agent's identity callback with vi.waitFor's default one-second
window. Every other connection wait in rpc-robustness.test.tsx passes
{ timeout: 10000 }. On a cold CI runner the first connection to a new
Durable Object took longer than a second, so "starts identity
comparison over when the requested address changes" failed on main
right after the 0.9.0 release merge with zero calls recorded. Give its
four waits the same ten seconds as the rest of the file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MiguelsPizza
MiguelsPizza merged commit 2e240a3 into main Sep 23, 2026
1 check passed
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