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

Overall build shown as red when all stages shown are green

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      A build where all stages were marked as green ended up red overall, but Blue Ocean shows no failures anywhere, even if I download the log file from Blue Ocean.

      However, if I go through to the legacy Jenkins view and download that log, it's a different log file which does include the error, which is apparently some internal OOME in Jenkins itself:

      [Pipeline] End of Pipeline
      [Bitbucket] Notifying pull request build result
      [Bitbucket] Build result notified
      java.lang.OutOfMemoryError: Java heap space
      	at com.sun.org.apache.xerces.internal.util.XMLStringBuffer.append(XMLStringBuffer.java:208)
      	at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.scanData(XMLEntityScanner.java:1428)
      	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanCDATASection(XMLDocumentFragmentScannerImpl.java:1655)
      	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3017)
      	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
      	at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:118)
      	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
      	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
      	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
      	at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
      	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
      	at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643)
      	at org.dom4j.io.SAXReader.read(SAXReader.java:445)
      	at org.dom4j.io.SAXReader.read(SAXReader.java:325)
      	at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:178)
      	at hudson.tasks.junit.TestResult.parse(TestResult.java:348)
      	at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:281)
      	at hudson.tasks.junit.TestResult.parse(TestResult.java:206)
      	at hudson.tasks.junit.TestResult.parse(TestResult.java:178)
      	at hudson.tasks.junit.TestResult.<init>(TestResult.java:143)
      	at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:146)
      	at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:118)
      	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3073)
      	at hudson.remoting.UserRequest.perform(UserRequest.java:211)
      	at hudson.remoting.UserRequest.perform(UserRequest.java:54)
      	at hudson.remoting.Request$2.run(Request.java:369)
      	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      	at java.lang.Thread.run(Thread.java:745)
      Caused: java.io.IOException: Remote call on U-Buildslave-docker06 failed
      	at hudson.remoting.Channel.call(Channel.java:1004)
      	at hudson.FilePath.act(FilePath.java:1069)
      	at hudson.FilePath.act(FilePath.java:1058)
      	at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114)
      	at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137)
      	at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167)
      	at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:50)
      	at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:23)
      	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      	at java.lang.Thread.run(Thread.java:748)
      Finished: FAILURE
      

      In this situation, I would expect Jenkins to at least show the reason on Blue Ocean somewhere.

      Ideally, an internal failure in Jenkins should not fail my build - if all stages are green then the overall build is green irrespective of what happens outside of the pipeline, in my opinion.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            trejkaz trejkaz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: