Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2018.4.24f1
2019.4
2020.1
2020.2
Issue ID
1262594
Regression
No
Multiple Playmode Tests return different results when run in batchmode
How to reproduce:
1. Unzip the project
2. Modify "RunTests" and "RunTests_Batchmode" .bat files (change the file paths so they are valid)
3. Run the .bat file (this takes from 30s to a few minutes, depending on the Editor version)
4. Observe the generated file in the path specified with -logFile attribute
Expected result: the error amount is 0 in both "TestResults" and "TestResults_Batchmode" files
Actual result: "TestResults_Batchmode" file has 6 errors
Reproducible with: 2018.4.25f1, 2019.4.4f1, 2020.1.0b16, 2020.2.0a18
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note:
Batchmode doesn't support coroutine or async code. Batchmode execute everything in a synchronous way.