Bamboo failing to display JUnit tests correctly
Symptoms
Junit results aren't being read/displayed by Bamboo.
AND
You may find the following errors in the logs,
java.io.IOException: Lock obtain timed out:
OR,
Stack Trace:
Method public com.atlassian.bamboo.resultsummary.BuildResultsSummary com.atlassian.bamboo.build.BuildResultsAction.getFailingSinceForTest(com.atlassian.bamboo.results.BuildResults,com.atlassian.bamboo.results.tests.TestResults) throws java.io.IOException threw an exception when invoked on com.atlassian.bamboo.build.ViewBuildResults@22942d
The problematic instruction:
----------
==> assignment: failingSinceBuild=action.getFailingSinceForTest(buildResult, testResult) [on line 263, column 21 in lib/components.ftl]
in user-directive cp.displayUnitTestsSummary [on line 181, column 17 in viewBuildResults.ftl]
----------
Java backtrace for programmers:
----------
freemarker.template.TemplateModelException: Method public com.atlassian.bamboo.resultsummary.BuildResultsSummary com.atlassian.bamboo.build.BuildResultsAction.getFailingSinceForTest(com.atlassian.bamboo.results.BuildResults,com.atlassian.bamboo.results.tests.TestResults) throws java.io.IOException threw an exception when invoked on com.atlassian.bamboo.build.ViewBuildResults@22942d
at freemarker.ext.beans.SimpleMethodModel.exec(SimpleMethodModel.java:136)
Cause
Bamboo was not shutdown properly, as a result the Lucene lock files were not cleaned up from the <Bamboo-Home>/index directory
Resolution
To fix this issue,
- Delete the lock files from the <Bamboo-home>/index directory.
- Restart Bamboo.
Note, you may need to perform a full re-index of Bamboo from, Administration -> reindexing if you notice that build telemetry is inconsistent.
Last modified on Jun 13, 2013
Powered by Confluence and Scroll Viewport.