Skip to content
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

Fixed unstable builds showing "0 tests started to fail" when build was unstable for other reasons. #165

Closed
wants to merge 1 commit into from

Conversation

drwelden
Copy link
Contributor

Fixed unstable builds showing "0 tests started to fail" when build was unstable for other reasons than test failure.

@otac0n
Copy link

otac0n commented Jun 17, 2011

This was a problem at our workplace. We had builds that were marked "unstable" because of CheckStyle violations. (Well, StyleCop, really)

What was happening is that if the build was unstable, but had no failures, it would report "0 tests have started to fail."

This is because it was assuming that an unstable build is due to tests, where, really, it can be caused by any plugin. The logic changes in the above commit address this.

@kohsuke
Copy link
Member

kohsuke commented Jun 17, 2011

Integrated toward 1.417. Thanks!

@kohsuke kohsuke closed this Jun 17, 2011
EstherAF pushed a commit to EstherAF/jenkins that referenced this pull request May 13, 2020
…76-20190708

Fix regression in security fixes for July 17, 2.176.x
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants