One machine is Mac with Unity Editor 2022.2.0 and another is Linux also with Unity 2022.2.0.
On both I run command (paths are different ofc). On Mac everything works fine however when testing exactly same commit on Linux I get code coverage 0 for all classes. Not sure what I may be doing wrong. Last time I tried this with completely fresh workspace to make sure it’s not broken however nothing changed. Also tests are run and results are properly updated - Unity is finding and executing those tests
As a workaround I have moved test execution to Mac for the time being however I’d still like to understand the reason why it is not working on this Linux worker. One thing that I have noticed as a difference is that on Mac csproj files are properly regenerated while on Linux they are not.
Hi @alterfenix . I’ve tried to reproduce your issue but was unable to. Would you be able to submit a bug report with your project or a small repro project and share the incident ID? I’ll then be able to open a bug if necessary or provide you with a solution to your issue.
Also, I’ve noticed that you’re using -burst-disable-compilation command line argument which is incorrect. It appears that our documentation had a typo. We’ll update it with a correct argument, which is –burst-disable-compilation (notice double dash at the front). Until we release a new package version with the fix, you will need to add both of them - one which actually works and the other which is (incorrectly) expected by the package.
I think I met the same problem, not sure about this command line option.
All other options is single dash but this use double dash, I think the requirement of double dash is more like a bug but the document?