Oliver

Can be easily fixed in a custom branch of addressables by modifying `BuildLayoutPrinter.cs`: ``` Index: BuildLayoutPrinter.cs =================================================================== --- BuildLayoutPrinter.cs (revision 30946) +++ BuildLayoutPrinter.cs (revision 30947) @@ -1,6 +1,7 @@ using...

This issue currently actually blocks us from running certain workflows through the unity runner, basically having to revert back to direct invocation of the unity editor, which makes configuration of...

This would be a really good addition to the plugin and make batch mode properly supported, as running `-batchmode` without `-quit` is a common and supported use-case.

I like the idea, too - one could record stack traces manually via the [StackTrace class](https://msdn.microsoft.com/en-us/library/system.diagnostics.stacktrace%28v=vs.110%29.aspx), and then pass traces to the next promise. But sounds like a pretty complicated...

Has this issue been solved? @romancin could you find a workaround? I had the same issue and could not upgrade due to the broken database connection.

The official unity test framework documentation tells you the details, see https://docs.unity3d.com/Packages/[email protected]/manual/reference-command-line.html tl;dr You'll have to separate test categories in the argument with a semicolon, so `Fast;Slow`