Search Issue Tracker

Won't Fix



Found in


Issue ID




[macOS] Unity freezes and never exits when running Test Runner from Command Line

Unity Test Runner


To reproduce:
1. Open Terminal window
2. Download user's project and unzip it
3. Launch Test Runner by using this command:
/(path to the folder with Unity's installation)/ -projectPath (path to the folder with user's project) -batchmode -runTests -testPlatform editmode -logFile (enter path where log file should be saved)

Expected result: After running a test Unity should close itself (terminate).
Actual result: Unity freezes and you have to Force Quit it.

Reproduced with: 5.6.3p4, 2017.1.2p1, 2017.2.0f3, 2017.3.0b4, 2018.1.0a1
Not reproducible with: 5.5.5p1

Won't fix because we don't support static test methods.

Comments (3)

  1. 86fed7bcef1e256b65779e3c0fa278c8?d=mm


    Jan 24, 2018 12:52

    Any news on this? Same happening here on windows and unity 2017.3

  2. 5f92d36c469415a66454d251a42e346f?d=mm


    Dec 18, 2017 07:43

    What version future release means? :)

  3. C38c4088ffef5a26eaf96afc81d931f4?d=mm


    Dec 12, 2017 14:15

    This issue is not reproducible with Unity 5.6.3f1 so my projects are currently stuck on that version as upgrading means that all continuous integration tests fail (due to timeout). Also, as a Unity upgrade of the projects is required to work with macOS High Sierra, this issue is also currently blocking an OS upgrade.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.