Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-390

build queue/log out of sync with dashboard status

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Sometimes when a build fails, the dashboard table shows the project as failed, yet the build queue is still there running, with that project in the queue, and if you view the log it hasn't finished yet, yet clearly (I'm guessing) the build already knows it has so updates it status, thus it looks out of sync, and lacks trust of correct status.

      below is the log for that area if it helps:

      2006-11-02 11:04:00,126 INFO [BAM::BuildPipeline::BuildExecutor] [AbstractBuilder] Starting to build 'NEM Jobbie'
      [build param details]
      2006-11-02 11:04:00,470 INFO [output stream pumper] [StreamToListPumper] [NMJ] Buildfile: build.xml
      2006-11-02 11:04:00,908 INFO [output stream pumper] [StreamToListPumper] [NMJ]
      2006-11-02 11:04:00,908 INFO [output stream pumper] [StreamToListPumper] [NMJ] init:
      2006-11-02 11:04:02,079 INFO [output stream pumper] [StreamToListPumper] [NMJ]
      2006-11-02 11:04:02,079 INFO [output stream pumper] [StreamToListPumper] [NMJ] stopTomcat:
      2006-11-02 11:04:02,251 INFO [output stream pumper] [StreamToListPumper] [NMJ] [echo] Stopping Tomcat in C:\dev\libraries\apache\jakarta\tomcat\5.5.17 running on port 8080...
      2006-11-02 11:04:37,422 INFO [SocketListener0-1] [BuildAwareInterceptor] Set build on BuildAware com.atlassian.bamboo.build.ViewCurrentRunningBuild: Build: com.atlassian.bamboo.build.LegacyBuildObject@c4e5222b
      2006-11-02 11:04:37,641 WARN [SocketListener0-1] [LocalizedTextUtil] Unable to find text for key 'Started' in 'class com.atlassian.bamboo.build.ViewCurrentRunningBuild' and locale 'en_US'
      2006-11-02 11:04:37,641 WARN [SocketListener0-1] [LocalizedTextUtil] Unable to find text for key 'Completed' in 'class com.atlassian.bamboo.build.ViewCurrentRunningBuild' and locale 'en_US'
      2006-11-02 11:04:37,641 WARN [SocketListener0-1] [LocalizedTextUtil] Unable to find text for key 'Time remaining' in 'class com.atlassian.bamboo.build.ViewCurrentRunningBuild' and locale 'en_US'
      2006-11-02 11:04:37,641 WARN [SocketListener0-1] [LocalizedTextUtil] Unable to find text for key 'Building' in 'class com.atlassian.bamboo.build.ViewCurrentRunningBuild' and locale 'en_US'
      2006-11-02 11:04:37,657 INFO [SocketListener0-1] [BuildAwareInterceptor] Set build on BuildAware com.atlassian.bamboo.build.ViewBuildActivityLog: Build: com.atlassian.bamboo.build.LegacyBuildObject@c4e5222b
      2006-11-02 11:04:38,719 INFO [SocketListener0-1] [BuildAwareInterceptor] Set build on BuildAware com.atlassian.bamboo.build.ViewBuildActivityLog: Build: com.atlassian.bamboo.build.LegacyBuildObject@c4e5222b
      2006-11-02 11:04:44,656 INFO [SocketListener0-1] [BuildAwareInterceptor] Set build on BuildAware com.atlassian.bamboo.build.ViewCurrentRunningBuild: Build: com.atlassian.bamboo.build.LegacyBuildObject@c4e5222b
      2006-11-02 11:04:44,781 WARN [SocketListener0-1] [LocalizedTextUtil] Unable to find text for key 'Started' in 'class com.atlassian.bamboo.build.ViewCurrentRunningBuild' and locale 'en_US'
      2006-11-02 11:04:44,797 WARN [SocketListener0-1] [LocalizedTextUtil] Unable to find text for key 'Completed' in 'class com.atlassian.bamboo.build.ViewCurrentRunningBuild' and locale 'en_US'
      2006-11-02 11:04:44,797 WARN [SocketListener0-1] [LocalizedTextUtil] Unable to find text for key 'Time remaining' in 'class com.atlassian.bamboo.build.ViewCurrentRunningBuild' and locale 'en_US'
      2006-11-02 11:04:44,797 WARN [SocketListener0-1] [LocalizedTextUtil] Unable to find text for key 'Building' in 'class com.atlassian.bamboo.build.ViewCurrentRunningBuild' and locale 'en_US'
      2006-11-02 11:04:44,797 INFO [SocketListener0-1] [BuildAwareInterceptor] Set build on BuildAware com.atlassian.bamboo.build.ViewBuildActivityLog: Build: com.atlassian.bamboo.build.LegacyBuildObject@c4e5222b
      2006-11-02 11:04:45,875 INFO [SocketListener0-1] [BuildAwareInterceptor] Set build on BuildAware com.atlassian.bamboo.build.ViewBuildActivityLog: Build: com.atlassian.bamboo.build.LegacyBuildObject@c4e5222b
      2006-11-02 11:05:02,703 INFO [BAM::BuildPipeline::BuildExecutor] [Command] err>
      2006-11-02 11:05:02,703 INFO [BAM::BuildPipeline::BuildExecutor] [Command] err>BUILD FAILED
      2006-11-02 11:05:02,703 INFO [BAM::BuildPipeline::BuildExecutor] [Command] err>C:\dev\work-dir\xml-data\build-dir\NMJ\build.xml:331: org.codehaus.cargo.container.ContainerException: Failed to stop the Tomcat 5.5.17 container. Check the [C:\dev\work-dir\xml-data\build-dir\NMJ\cargo_output.log] file containing the container logs for more details.
      2006-11-02 11:05:02,703 INFO [BAM::BuildPipeline::BuildExecutor] [Command] err>
      2006-11-02 11:05:02,703 INFO [BAM::BuildPipeline::BuildExecutor] [Command] err>Total time: 1 minute 2 seconds
      2006-11-02 11:05:02,703 INFO [BAM::BuildPipeline::BuildExecutor] [AbstractBuilder] Completed building build "NEM Jobbie" return code = 0
      2006-11-02 11:05:02,719 ERROR [BAM::BuildPipeline::BuildExecutor] [AntXmlTestResultsParser] Failed to parse xml test results
      org.xml.sax.SAXParseException: Premature end of file.
      at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1183)
      at com.atlassian.bamboo.builder.AntXmlTestResultsParser.parse(AntXmlTestResultsParser.java:63)
      at com.atlassian.bamboo.builder.AntJunitTestReportCollector.collect(AntJunitTestReportCollector.java:35)
      at com.atlassian.bamboo.builder.AbstractBuilder$1.visitFile(AbstractBuilder.java:226)
      at com.atlassian.bamboo.utils.FileVisitor.visitAllFilesInADirectory(FileVisitor.java:61)
      at com.atlassian.bamboo.utils.FileVisitor.visitFilesThatMatch(FileVisitor.java:50)
      at com.atlassian.bamboo.builder.AbstractBuilder.collateTestResults(AbstractBuilder.java:239)
      at com.atlassian.bamboo.builder.AbstractBuilder.build(AbstractBuilder.java:199)
      at com.atlassian.bamboo.builder.DefaultBuildExecutor.build(DefaultBuildExecutor.java:120)
      at com.atlassian.bamboo.builder.DefaultBuildExecutor.doTask(DefaultBuildExecutor.java:66)
      at com.atlassian.bamboo.container.BambooTask.run(BambooTask.java:33)
      at java.lang.Thread.run(Unknown Source)
      2006-11-02 11:05:02,734 INFO [BAM::BuildPipeline::BuildExecutor] [DefaultBuildExecutor] Build log size: 15
      2006-11-02 11:05:02,734 INFO [BAM::BuildPipeline::BuildExecutor] [DefaultBuildExecutor] Setting build artifacts
      2006-11-02 11:05:02,781 INFO [BAM::BuildPipeline::BuildCompleteNotifier] [DefaultTestCaseResultsIndexer] Indexing build ... NMJ986, took: 47

      Somewhere in the middle of this (usually the log is holding at the stoptomcat bit above) it says it's running but the dash says it's failed and finished.

        1. out of sync.bmp
          1.59 MB

            [BAM-390] build queue/log out of sync with dashboard status

            MarkC added a comment -

            This should now no longer be a problem with the queues being rewrittem

            MarkC added a comment - This should now no longer be a problem with the queues being rewrittem

            Riaz Khanmohamed added a comment -

            Hopefully the debug code will help. I'm afraid that folder is fairly large, in the region of 400mb+ so i can't zip it all. You believe it's just one or the current one that's causing this? Obviously without more debug info I guess you can't tell, so I'll hold this off until 0.6

            Riaz Khanmohamed added a comment - Hopefully the debug code will help. I'm afraid that folder is fairly large, in the region of 400mb+ so i can't zip it all. You believe it's just one or the current one that's causing this? Obviously without more debug info I guess you can't tell, so I'll hold this off until 0.6

            MarkC added a comment -

            Riaz,

            I think there may be a few issues here. The hanging of queues after it failed should now be fixed (see BAM-95). When an exception happens (as it did in your case), builds didn't always complete properly. In 0.6, builds should now fail if an exception occurs.

            2006-11-02 11:05:02,719 ERROR [BAM::BuildPipeline::BuildExecutor] [AntXmlTestResultsParser] Failed to parse xml test results
org.xml.sax.SAXParseException: Premature end of file.
at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1183)
at com.atlassian.bamboo.builder.AntXmlTestResultsParser.parse(AntXmlTestResultsParser.java:63)
at com.atlassian.bamboo.builder.AntJunitTestReportCollector.collect(AntJunitTestReportCollector.java:35)
at com.atlassian.bamboo.builder.AbstractBuilder$1.visitFile(AbstractBuilder.java:226)
at com.atlassian.bamboo.utils.FileVisitor.visitAllFilesInADirectory(FileVisitor.java:61)
at com.atlassian.bamboo.utils.FileVisitor.visitFilesThatMatch(FileVisitor.java:50)
at com.atlassian.bamboo.builder.AbstractBuilder.collateTestResults(AbstractBuilder.java:239)
at com.atlassian.bamboo.builder.AbstractBuilder.build(AbstractBuilder.java:199)
at com.atlassian.bamboo.builder.DefaultBuildExecutor.build(DefaultBuildExecutor.java:120)
at com.atlassian.bamboo.builder.DefaultBuildExecutor.doTask(DefaultBuildExecutor.java:66)
at com.atlassian.bamboo.container.BambooTask.run(BambooTask.java:33)
at java.lang.Thread.run(Unknown Source)

            Are you getting this error consistently? If so is it possible to zip up & attach the directory under C:\dev\work-dir\xml-data\build-dir\NMJ where the you've set up the build to look for test files? ie */test-reports/.xml, or whatever your Build Configuration says.

            From the code, there seems to be an XML file in there that's not quite the right format, or is empty. I've added some code in 0.6 now that should better debug which file it died on as well.

            Cheers,

            Mark C

            MarkC added a comment - Riaz, I think there may be a few issues here. The hanging of queues after it failed should now be fixed (see BAM-95 ). When an exception happens (as it did in your case), builds didn't always complete properly. In 0.6, builds should now fail if an exception occurs. 2006-11-02 11:05:02,719 ERROR [BAM::BuildPipeline::BuildExecutor] [AntXmlTestResultsParser] Failed to parse xml test results org.xml.sax.SAXParseException: Premature end of file. at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1183) at com.atlassian.bamboo.builder.AntXmlTestResultsParser.parse(AntXmlTestResultsParser.java:63) at com.atlassian.bamboo.builder.AntJunitTestReportCollector.collect(AntJunitTestReportCollector.java:35) at com.atlassian.bamboo.builder.AbstractBuilder$1.visitFile(AbstractBuilder.java:226) at com.atlassian.bamboo.utils.FileVisitor.visitAllFilesInADirectory(FileVisitor.java:61) at com.atlassian.bamboo.utils.FileVisitor.visitFilesThatMatch(FileVisitor.java:50) at com.atlassian.bamboo.builder.AbstractBuilder.collateTestResults(AbstractBuilder.java:239) at com.atlassian.bamboo.builder.AbstractBuilder.build(AbstractBuilder.java:199) at com.atlassian.bamboo.builder.DefaultBuildExecutor.build(DefaultBuildExecutor.java:120) at com.atlassian.bamboo.builder.DefaultBuildExecutor.doTask(DefaultBuildExecutor.java:66) at com.atlassian.bamboo.container.BambooTask.run(BambooTask.java:33) at java.lang.Thread.run(Unknown Source) Are you getting this error consistently? If so is it possible to zip up & attach the directory under C:\dev\work-dir\xml-data\build-dir\NMJ where the you've set up the build to look for test files? ie * /test-reports/ .xml , or whatever your Build Configuration says. From the code, there seems to be an XML file in there that's not quite the right format, or is empty. I've added some code in 0.6 now that should better debug which file it died on as well. Cheers, Mark C

            Riaz Khanmohamed added a comment -

            actually, as it turns out, the dashboard is showing the latest completed build, while it's actually building the next version in the queue but not showing it on the dashboard unit as in process - like it can't see the latest entry or something

            Riaz Khanmohamed added a comment - actually, as it turns out, the dashboard is showing the latest completed build, while it's actually building the next version in the queue but not showing it on the dashboard unit as in process - like it can't see the latest entry or something

              Unassigned Unassigned
              0aac02679fc3 Riaz Khanmohamed
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: