[JIRA] [xunit] (JENKINS-18341) xUnit cannot parse JUnit output from a Gradle build because of empty element
Kyle Mahan
created JENKINS-18341
xUnit cannot parse JUnit output from a Gradle build because of empty element
Issue Type:
Bug
Affects Versions:
current
Assignee:
Gregory Boissinot
Attachments:
TEST-MyTest.xml
Components:
xunit
Created:
13/Jun/13 7:23 PM
Description:
Running a simple Gradle configuration, the xUnit plugin cannot validate JUnit output files because the element is empty. There does not appear to be a canonical schema for JUnit XML output, but informal sources (eg, http://windyroad.com.au/2011/02/07/apache-ant-junit-xml-schema/) allow 0..n tags inside of a tag.
Jenkins gives the following output:
Jun 12, 2013 7:00:13 PM com.thalesgroup.hudson.plugins.xunit.service.XUnitService errorSystemLogger
SEVERE: [xUnit] - The result file 'C:\Programs\jenkins\jobs\Midas Testing\workspace\ssi\build\test-results\TEST-com.stottlerhenke.ssi.report.io.TestReportConfig.xml' for the metric 'JUnit' is not valid. The result file has been skipped.
Jun 12, 2013 7:00:13 PM com.thalesgroup.hudson.plugins.xunit.service.XUnitService warningSystemLogger
WARNING: [xUnit] - The file 'C:\Programs\jenkins\jobs\Midas Testing\workspace\ssi\build\test-results\TEST-com.stottlerhenke.ssi.report.io.TestReportConfig.xml' is an invalid file.
Jun 12, 2013 7:00:13 PM com.thalesgroup.hudson.plugins.xunit.service.XUnitService errorSystemLogger
I am attaching a sample file that fails to validate with com.thalesgroup.dtkit.junit.model.JUnitModel.OUTPUT_JUNIT_6. Validating this file gives the following error:
At line 3 of file:///C:/Users/kmahan/Projects/JUnitTest/build/test-results/TEST-MyTest.xml:cvc-complex-type.2.4.b: The content of element 'properties' is not complete. One of '{"":property}' is expected.
My proposed fix would add minOccurs="0" to the properties element in junit-6.xsd (and possibly the other junit schemas as well?) to allow for empty properties elements.
Environment:
Windows 7
Project:
Jenkins
Labels:
xunit
testing
plugin
Priority:
Minor
Reporter:
Kyle Mahan
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16605) Multi-configuration Maven project fails to build on Windows if label is "os"
Kyle Mahan created JENKINS-16605 Multi-configuration Maven project fails to build on Windows if label is "os" Issue Type: Bug Affects Versions: current Assignee: rsandell Components: matrix, maven, multi-slave-config Created: 01/Feb/13 9:23 PM Description: Starting with version 1.50, a multi-configuration project with one axis of type Slaves, with the label "os" fails to build on Windows with the output: Started by upstream project "TestMatrix" build number 4 originally caused by: Started by user anonymous [EnvInject] - Loading node environment variables. Building on master in workspace C:\Programs\jenkins\jobs\TestMatrix\workspace\os\win [win] $ mvn.bat -Dos=win install [INFO] Scanning for projects... [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Invalid task 'win': you must specify a valid lifecycle phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion:goal [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: < 1 second [INFO] Finished at: Fri Feb 01 13:15:25 PST 2013 [INFO] Final Memory: 1M/15M [INFO] Build step 'Invoke top-level Maven targets' marked build as failure Finished: FAILURE mvn.bat almost seems to interpret "-Dos=win" as "-Dos= win" (two separate arguments). The same command works from the command-line. To reproduce, create a new Multi-configuration project. Select Add Axis > Slaves. Set the label to "os" and select a node labeled "win". Select Add Build Step > Invoke Top level maven target. Save and build. Environment: Windows 7, Maven 2.2.1 Project: Jenkins Labels: maven windows labels multi-configuration matrix Priority: Major Reporter: Kyle Mahan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
