Skip to content

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

Closed
drwelden wants to merge 1 commit into
jenkinsci:masterfrom
drwelden:master
Closed

Fixed unstable builds showing "0 tests started to fail" when build was unstable for other reasons.#165
drwelden wants to merge 1 commit into
jenkinsci:masterfrom
drwelden:master

Conversation

@drwelden
Copy link
Copy Markdown
Contributor

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

@otac0n
Copy link
Copy Markdown

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
Copy Markdown
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

Development

Successfully merging this pull request may close these issues.

3 participants