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
- Material's icon doesn't fit the "Material preview not available" text when the Material doesn't have a preview
- Two fields in GLTF Importer Inspector are misaligned with other settings
- Duplicate image components can be added in m_TrackedTextureLess images and are never removed
- Cancelling a Package installation leads to invisible compilation errors preventing the user to enter Play Mode when the “Cancel” button is clicked, and does not actually cancel the package install as it appears in the Project after the Editor is restarted
- NullReferenceException occurs when searching presets in “Select Preset” window after selecting a GLTF Importer preset
Resolution Note:
Batchmode doesn't support coroutine or async code. Batchmode execute everything in a synchronous way.