Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Failing tests don't fail build when warningsAsErrors is false
See original GitHub issueWe’ve started setting warningsAsErrors to false in our builds of Arcade projects because that’s what we did before, and we have some warnings that would currently cause us to start failing, but when we do this test failures don’t fail the build because they’re only logged as warnings. I suspect this is caused by this line, where LogStandardErrorAsError="false". I’ve noticed that that’s set that way in a couple different Exec’s, so possibly this is not the only area affected.
Repro:
- Clone git@github.com:aspnet/Extensions.git
- git checkout rybrande/Arcade
- .\build.cmd
That takes a while to run, but if I’m right it should replicated against any arcade repo with a failing test against which warnaserrors=false was passed.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yeah, seems like a bug in msbuild to me.
Next step is to find and reference the tracking msbuild bug (assuming there is one)