Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0p2
Issue ID
955748
Regression
No
Build process does not set ERRORLEVEL in non-batchmode
To reproduce:
1. Adjust the paths in the batch file to your local Unity path.
2. Run the batch file to build in -batchmode
3. Note the window should go red to indicate ERRORLEVEL was 1.
4. Press a key to continue, the batch file will then build without -batchmode.
5. Note the window goes green to indicate ERRORLEVEL was 0.
Expected: -batchmode and non batchmode should set the same return value.
Reproduced in 5.6.4f1, 2017.1.0p5, 2017.3.0b3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment