Skip to content

test: give the playmode integration tests 5 s to receive an event - #2906

Draft
bitsandfoxes wants to merge 1 commit into
ci/job-timeoutsfrom
test/playmode-event-timeout
Draft

bitsandfoxes wants to merge 1 commit into
ci/job-timeoutsfrom
test/playmode-event-timeout

Conversation

@bitsandfoxes

@bitsandfoxes bitsandfoxes commented Oct 25, 2026 •

Copy link
Copy Markdown
Contributor

The playmode integration tests now give an event 5 s to reach the test HTTP handler instead of 1 s, so a slow CI runner no longer fails them.

Job 119764822362 failed BugFarmScene_MultipleSentryInit_SendEventForTheLatest with Expected: not equal to <string.Empty>. The handler logged timed out waiting for an event at 57.505 and returns event 17 ms later, at 57.522. The other 372 tests passed, and the next run on the branch was green.

GetEvent returns as soon as the event shows up, so a passing test isn't any slower. Only a test that's failing anyway waits the full 5 s. The exception is the sanity check in that same test, which expects the first handler to receive nothing. It would always wait out the full timeout, so it keeps its 1 s.

Stacked on #2905.

CI evidence: the playmode tests passed in the Build Unity SDK job of run 40228677752, on #2908 directly above this. This PR's own run was cancelled when the Linux native SDK build broke on the .NET 9 install (#2907).

Rebased onto #2907: run 40291024676 is green on the first attempt, playmode tests included.

🤖 Generated with Claude Code

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