Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-48250

junit step failures hidden in console output

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: junit-plugin
    • Labels:
      None
    • Environment:
      Jenkins ver. 2.73.3, Blue Ocean 1.3.2
    • Similar Issues:
    • Epic Link:
    • Sprint:
      Blue Ocean 1.4 - beta 3

      Description

      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'
              }
          }
      }
      
      

        Attachments

          Issue Links

            Activity

            Hide
            abayer Andrew Bayer added a comment -
            Show
            abayer Andrew Bayer added a comment - Got it - https://github.com/jenkinsci/junit-plugin/pull/93 fixes it.
            Hide
            jamesdumay James Dumay added a comment -

            Woohoo! Nice one Andrew Bayer

            Show
            jamesdumay James Dumay added a comment - Woohoo! Nice one Andrew Bayer
            Hide
            abayer Andrew Bayer added a comment -

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

            Show
            abayer Andrew Bayer added a comment - Fixed in next release (1.24, probably coming end of this week)
            Hide
            scm_issue_link 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

            Show
            scm_issue_link 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
            Hide
            jglick 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.

            Show
            jglick 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.

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: