Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
1
Found in
2023.1.0a1
Issue ID
UUM-1150
Regression
No
"Test execution timed out. No activity received from the player in 600 seconds" error appears when running WebGL tests
Reproduction steps:
1. Open the attached "Project.zip" project
2. Open the "Test Runner" window (Window > General > Test Runner)
3. Select the "Play Mode" option
4. Press the "Run All Tests (WebGL)" button
Expected result: Tests run successfully, the Player runs in the browser, and the "All test(s) succeeded" message is displayed
Actual result: Tests hang on "Building native binary with IL2CPP..." and the "Test execution timed out. No activity received from the player in 600 seconds" error appears in the Console after 10 minutes
Reproducible with: 2019.4.36f1, 2020.3.33f1, 2021.3.0f1, 2022.1.0b15, 2022.2.0a9
Reproducible with: macOS, Windows
Reproducible with: Google Chrome, Firefox
Notes:
- "Test execution timed out" error appears only after the first time running tests
- When running tests multiple times, results can be as such:
1. "An unexpected error happened while running tests." and other errors appear in the Console
2. Tests run successfully, the Player runs in the browser, but the page becomes unresponsive, or errors occur
- Tests run successfully on a standalone platform
Comments (1)
-
ProtoTerminator
Dec 12, 2022 02:27
This is a regression. It works in 2018.4.36. Please fix.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Client And Server” shown without spaces in Active Scenario window
- [Linux] Mouse cursor gets stuck at the edge of the screen when trying to pan in the Scene view
- Docked Multiplayer Play Mode window disappears when switching back to a saved Editor layout
- Audio files fail to be imported when the file path is 260 characters or longer
- Error SGICE002 is wrongly shown when more than one argument is passed into GetComponentRW()
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2023.1.X):
There are no fixes planned for this Bug