-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(ci): correctly report appveyor failures #2238
Conversation
ae77dfb
to
43e3f57
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. unless @hansl spots something himself.
There's something wrong still, at least on windows. The CI should fail, and it isn't failing. |
It's not a windows problem apparently, |
868b98b
to
8f4c898
Compare
Turns out that you must manually set the exit code when not using the default reporter. |
8f4c898
to
949138c
Compare
949138c
to
a57773c
Compare
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
No description provided.