tag:help.appveyor.com,2012-11-13:/discussions/problems/16812-build-failing-for-no-obvious-reasonAppVeyor: Discussion 2018-10-18T22:03:50Ztag:help.appveyor.com,2012-11-13:Comment/460866572018-09-16T07:10:00Z2018-09-16T07:10:00ZBuild failing for no obvious reason...<div><p>What about the compilation errors starting <a href="https://ci.appveyor.com/project/xinchen10/amqpnetlite/build/2.0.0.210/job/eh4iywr69ta1vh2r#L750">here</a>?</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/460866572018-09-16T09:38:57Z2018-09-16T09:38:57ZBuild failing for no obvious reason...<div><p>oh my... that's embarrassing...<br>
You are obviously right and that is the cause for the failure.</p>
<p>I swear I've look at the log a number of times and totally missed that!</p>
<p>Suggestion for a future enhancement (very handy for dumbs like me) highlight the build error messages with a red colour. It can be difficult to spot those, specially in logs with hundreds of thousands lines on which the error doesn't spot the build immediately and, therefore, the root cause is not right at the very end of the log output.</p></div>José Simõestag:help.appveyor.com,2012-11-13:Comment/460866572018-09-16T16:18:09Z2018-09-16T16:18:09ZBuild failing for no obvious reason...<div><p>If you remove the pipe to <code>Write-Output</code> does that compilation error still remain <em>un</em>-highlighted?</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/460866572018-09-19T13:32:00Z2018-09-19T13:32:00ZBuild failing for no obvious reason...<div><p>I've removed the pipe but I can't see any highlight on compilation/build errors...<br>
Please check it here: <a href="https://ci.appveyor.com/project/xinchen10/amqpnetlite/build/2.0.0.218/job/yqs9b30kreptelm8">https://ci.appveyor.com/project/xinchen10/amqpnetlite/build/2.0.0.2...</a></p></div>José Simõestag:help.appveyor.com,2012-11-13:Comment/460866572018-09-19T17:08:25Z2018-09-19T17:08:25ZBuild failing for no obvious reason...<div><p>You could try changing your <code>build_script:</code> from powershell to cmd. I'm not an expert on these shell interaction subtleties, but it seems the error is being interpreted differently once returned to build machine's custom powershell host. Probably could also explicity add a <code>$LastExitCode</code> check in the powershell script to more explicitly detect and present errors in a more readable way.</p></div>Owen McDonnell