[JIRA] (JENKINS-37663) Build is not marked as UNSTABLE even though failures are found

[me@joshma.com (JIRA)]

Joshua Ma created an issue

Jenkins / JENKINS-37663 Build is not marked as UNSTABLE even though failures are found Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 2016/Aug/24 10:03 PM Environment: Jenkins 2.19 junit 1.18 Labels: plugins Priority: Major Reporter: Joshua Ma I'm using JUnitResultsArchive to record test results, and I'm seeing a weird bug where there are failures reported but the build is not marked unstable. This is via Jenkins pipeline, and immediately after the step, I'm echoing the build result: step([$class: 'JUnitResultArchiver', testResults: 'build/xunit.xml']) echo ">>> BUILD RESULT ${currentBuild.result}" I can confirm that a test failed in that step, and the result printed is ">>> BUILD RESULT null" This doesn't always happen - in some other runs, the result is UNSTABLE as expected. Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[global@tolar.ws (JIRA)]

robert tolar haining commented on JENKINS-37663

Re: Build is not marked as UNSTABLE even though failures are found I'm seeing the same thing.

Add Comment

[me@joshma.com (JIRA)]

Joshua Ma commented on JENKINS-37663

Re: Build is not marked as UNSTABLE even though failures are found

This is still affecting us - I have two builds (pipeline runs) back to back, where the second build does not change anything other than static images (not test related). Both builds have 1 test failing, but the first is SUCCESS while the second is UNSTABLE.

Add Comment

[girardc79@gmail.com (JIRA)]

Chris Girard updated an issue

Jenkins / JENKINS-37663

Build is not marked as UNSTABLE even though failures are found

Change By: Chris Girard Attachment: screenshot-1.png

Add Comment

[girardc79@gmail.com (JIRA)]

Chris Girard commented on JENKINS-37663

Re: Build is not marked as UNSTABLE even though failures are found We are also seeing this in our builds. We are using the multi-branch pipeline (i.e. Jenkinsfile) with the "junit" step. We have also seen back-to-back builds where the actual failing tests did not change, but one build was marked unstable while the other was passing. Peculiar symptom: On the build status page for such builds, note the "Test Result (no failures)" followed immediately by the "Show All Failed Tests >>>" link: Clicking the Show All link expanded to the 39 failing tests we had for that build.

Add Comment

[bitwiseman@gmail.com (JIRA)]

Liam Newman closed an issue as Fixed

Bulk closing resolved issues.

Jenkins / JENKINS-37663

Build is not marked as UNSTABLE even though failures are found

Change By: Liam Newman Status: Resolved Closed

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)