Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.2.0p1
Issue ID
990864
Regression
No
Fix Integration Test stalls after failure to connect to WindowServer
When running the Unity Integration Test suite to run integration tests on real devices on a build machine, the tests stall indefinitely.
This problem occurs when a user is not logged into the build machine when the tests are run. The failure that occurs is:
>RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL
Instead of stalling, if this error is encountered, could Unity instead exit instead of idling. Alternatively, if the integration tests could be run with -nographics or without a logged in user, we expect this might work as well.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2018.2.X):
Closing the issue based on its age and lack of information to reproduce