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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (2018.2.X):
Closing the issue based on its age and lack of information to reproduce