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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note (2018.2.X):
Closing the issue based on its age and lack of information to reproduce