• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • junit-plugin
    • None
    • Jenkins ver. 2.73.3, Blue Ocean 1.3.2
    • Blue Ocean 1.4 - beta 3

      See the attached screenshots, for the Jenkinsfile below.

      I could have sworn this was fixed but I guess I was wrong

      pipeline {
          agent { docker 'maven:3-alpine' }
          stages {
              stage('Build') {
                  steps {
                      sh 'mvn -B -U -e clean install'
                  }
              }
          }
          post {
              always {
                  junit '**/surefire-reports/**/*.xml'
              }
          }
      }
      
      

          [JENKINS-48250] junit step failures hidden in console output

          James Dumay added a comment -

          I wish the Pipeline model was sane.

          James Dumay added a comment - I wish the Pipeline model was sane.

          Andrew Bayer added a comment -

          What exactly is expected here?

          Andrew Bayer added a comment - What exactly is expected here?

          James Dumay added a comment -

          abayer would you mind investigating?

          James Dumay added a comment - abayer would you mind investigating?

          Andrew Bayer added a comment -

          Ah, it looks like that error is being thrown in an exception in JUnitParser but not going to the listener for the step. Need to figure out how to capture that.

          Andrew Bayer added a comment - Ah, it looks like that error is being thrown in an exception in JUnitParser but not going to the listener for the step. Need to figure out how to capture that.

          James Dumay added a comment -

          Thanks abayer

          James Dumay added a comment - Thanks abayer

          Andrew Bayer added a comment -

          Andrew Bayer added a comment - Got it - https://github.com/jenkinsci/junit-plugin/pull/93 fixes it.

          James Dumay added a comment -

          Woohoo! Nice one abayer

          James Dumay added a comment - Woohoo! Nice one abayer

          Andrew Bayer added a comment -

          Fixed in next release (1.24, probably coming end of this week)

          Andrew Bayer added a comment - Fixed in next release (1.24, probably coming end of this week)

          Code changed in jenkins
          User: Andrew Bayer
          Path:
          src/main/java/hudson/tasks/junit/pipeline/JUnitResultsStepExecution.java
          src/test/java/hudson/tasks/junit/pipeline/JUnitResultsStepTest.java
          http://jenkins-ci.org/commit/junit-plugin/2234f40d3919e4087122eb5195cc679f3f154309
          Log:
          [FIXED JENKINS-48250] Log errors from JUnit parsing to FlowNode log

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Andrew Bayer Path: src/main/java/hudson/tasks/junit/pipeline/JUnitResultsStepExecution.java src/test/java/hudson/tasks/junit/pipeline/JUnitResultsStepTest.java http://jenkins-ci.org/commit/junit-plugin/2234f40d3919e4087122eb5195cc679f3f154309 Log: [FIXED JENKINS-48250] Log errors from JUnit parsing to FlowNode log

          Jesse Glick added a comment -

          This is a bug in Blue Ocean, not in junit. There is no expectation in general that details of a step failure would be present in its LogAction, if it even has one. Blue Ocean should be displaying the ErrorAction message. I am reverting the bogus logic and commenting out the bogus test as part of the external storage work.

          Jesse Glick added a comment - This is a bug in Blue Ocean, not in junit . There is no expectation in general that details of a step failure would be present in its LogAction , if it even has one. Blue Ocean should be displaying the ErrorAction message. I am reverting the bogus logic and commenting out the bogus test as part of the external storage work.

            abayer Andrew Bayer
            rtyler R. Tyler Croy
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: