Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2017.4.1f1
2018.3.0a1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1183461
Regression
Yes
Compiler Output warnings and errors are placed outside of the stderr section when building a project
How to reproduce:
1. Download the user-submitted project(2017test)
2. Build it via CMD/Terminal along with the -batchmode argument
3. Open the Editor.log and scroll down to see the Compiler Output
Expected result: the errors are between -----CompilerOutput:-stderr---------- and -----EndCompilerOutput---------------
Actual result: the errors are above -----CompilerOutput:-stderr---------- and -----EndCompilerOutput---------------
Reproducible with: 2018.3.0a1, 2018.4.8f1, 2019.2.5f1, 2019.3.0b3, 2020.1.0a4
Not reproducible with: 2017.4.32f1, 2018.2.21f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Incorrect Burst Exception Control Flow in Editor due to Mono Handling of calli instruction
- [Linux] Packman options to add package from Git URL doesn't always show the window directly below the + button
- "UnityEngine.SystemInfo.processorFrequency" logs a value of 0 on M1 macs
- Editor redirects to a broken page when pressing question mark "?" in the Inspector window
- Editor directs to non-existent page when pressing "Learn more..." for Asset Pipeline
Add comment