Stalled builds following a "Cleanup mono" after running unit tests using Unity 2017.3f3

Potentially related issue: https://forum.unity.com/threads/bui...loud-using-engine-version-2017-2-0b11.497091/

All of the builds on one project has stalled after running unit tests for the past day, leading to cancelled builds. It seems to stall on "Cleanup mono".

I've had this issue before in older Unity releases, and it's only occurred when the MonoBleedingEdge runtime is used as a part of the project.

 

I just confirmed it. It only happens when running unit tests on with MonoBleedingEdge enabled.

 

Seeing the same problem after upgrading from 2017.1 to 2017.3 on our build machine.

How do you turn off MonoBleedingEdge for unit tests?

 

I simply turned off unit tests and ran them locally, as it seems to only stall on Unity Cloud Build, before making any big merges,but I would much rather be able to run these tests as a part of continuous integration.

 

Thanks Ollie, we aren't actually using Cloud Build, we are just running the tests via the command line with these arguments:
-nographics
-batchmode
-runEditorTests

We are indeed using .NET 4.6 Equivalent, and can't go back to 3.5, so we will disable tests while we wait for a patch

 

Is there any update or an ETA on when this issue might be fixed?

 

I'm still seeing this issue on 2019.2.17f1, sporadically, unrelated to running unit tests. The editor just doesn't close reliably even though we're using "-quit -batchMode"

 

Since that issue is unrelated to cloud build, your best chance of getting a fix would be to submit a replication using the Editor (Help -> Report a Bug).