[
https://issues.jenkins-ci.org/browse/JENKINS-12900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gbois resolved JENKINS-12900.
-----------------------------
Resolution: Fixed
These kind of errors are aimed at the integrators/administrators.
xUnit have chosen to not provide these information in the Job log.
These details can be displayed in the global configuration through the
following actions:
Manage Jenkins > System Log > Add new log recorder.
Give a name as 'xUnit Logger' and add the following logger:
* XUnitService for a severity as 'all'
> Better feedback needed when a report can't be processed
> -------------------------------------------------------
>
> Key: JENKINS-12900
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12900
> Project: Jenkins
> Issue Type: Bug
> Components: xunit
> Reporter: Chris Withers
> Assignee: gbois
>
> The following is simply not enough to figure out what is wrong with a report
> file:
> [xUnit] [INFO] - Starting to record.
> [xUnit] [INFO] - Processing JUnit
> [xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern
> '**/valgrind-junit.xml' relative to
> '/home/jenkins/workspace/workspace/valgrind' for the testing framework
> 'JUnit'.
> [xUnit] [ERROR] - The result file
> '/home/jenkins/workspace/workspace/valgrind/valgrind-junit.xml' for the
> metric 'JUnit' is not valid. The result file has been skipped.
> [xUnit] [INFO] - Setting the build status to FAILURE
> [xUnit] [INFO] - Stopping recording.
> It really needs to say at least what line caused the problem, and preferably
> what it thought the problem was.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
