Issue Details (XML | Word | Printable)

Key: BAM-235
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Mark Chaimungkalanont [Atlassian]
Reporter: Riaz Khanmohamed
Votes: 0
Watchers: 0
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Bamboo

Ant xml files can't be read

Created: 19/Sep/06 12:01 PM   Updated: 21/Sep/06 08:08 PM
Component/s: Builders (Other)
Affects Version/s: 0.3
Fix Version/s: 0.5

Time Tracking:
Original Estimate: 4 hours
Original Estimate - 4 hours
Remaining Estimate: 1 hour
Time Spent - 3 hours Remaining Estimate - 1 hour
Time Spent: 3 hours
Time Spent - 3 hours Remaining Estimate - 1 hour

Issue Links:
Reference
 

Participants: Mark Chaimungkalanont [Atlassian] and Riaz Khanmohamed
Since last comment: 2 years, 15 weeks, 5 days ago
Number of comments: 4
Internal Priority: 2. High
Labels:


 Description  « Hide
Started suddenly getting :

2006-09-19 16:41:39,546 ERROR [BJ::BuildPipeline::BuildExecutor] [AntXmlTestResultsParser] Failed to parse xml test results
java.lang.NullPointerException
at com.atlassian.bamboo.builder.AntXmlTestResultsParser$ErrorElementParser.endElement(AntXmlTestResultsParser.java:191)
at com.atlassian.bamboo.configuration.DefaultContentHandler.endElement(DefaultContentHandler.java:63)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:579)
at org.apache.xerces.impl.XMLNamespaceBinder.handleEndElement(XMLNamespaceBinder.java:897)
at org.apache.xerces.impl.XMLNamespaceBinder.endElement(XMLNamespaceBinder.java:643)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.java:1972)
at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:878)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDocumentFragmentScannerImpl.java:1144)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:987)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1445)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:333)
at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:524)
at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:580)
at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1169)
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:227)
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:240)
at com.atlassian.bamboo.builder.AbstractBuilder.build(AbstractBuilder.java:200)
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)

This is due to an error on running the tests (testcase compiled to wrong java version). The xml to me looks fine...

I'll attach a copy of one if you make this entry private (unless you've already fixed it)

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
[ Permlink | « Hide ]
Mark Chaimungkalanont [Atlassian] added a comment - 20/Sep/06 07:56 PM
Riaz,

I've made the issue private. Could you please attach your zipped up test-results directory to this issue?

This is due to an error on running the tests (testcase compiled to wrong java version).

I'm guessing you mean that's what happened with the ant build?

Cheers,

Mark C


[ Permlink | « Hide ]
Riaz Khanmohamed added a comment - 21/Sep/06 03:13 AM
During the build, whereby each test failed miserably (test case was invalid) it threw this error trying to read the ant xml, even though they look valid.

I've attached one file - they're all identical. Wondering if there's something your code is expecting or not expecting that's calling this - the system-out and system-err entries are basically emtpy, and we have an <error > tag not normally shown in the ant files.


[ Permlink | « Hide ]
Mark Chaimungkalanont [Atlassian] added a comment - 21/Sep/06 04:41 AM
Riaz,

Thanks for that. It seems our code expects the <error> element to always be inside a <testcase> element. Which it is not in this case.

We'll get this sorted for you.

Cheers,

Mark C


[ Permlink | « Hide ]
Mark Chaimungkalanont [Atlassian] added a comment - 21/Sep/06 08:06 PM
Riaz,

This should be resolved now. Although the XML doesn't have any information on the actual test case that failed at the moment, we've added error message to a dummy testCase inside the affected test suite (so you should be able to see the error).

This will work from 0.5 onwards

Cheers,

Mark C
Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.2-#335) - Bug/feature request - Atlassian news - Contact Administrators