[ 
https://issues.jenkins-ci.org/browse/JENKINS-13063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161639#comment-161639
 ] 

kbond commented on JENKINS-13063:
---------------------------------

Looks the be the same issue, I will try out the latest release.
                
> Test report does not include all matching result xml files
> ----------------------------------------------------------
>
>                 Key: JENKINS-13063
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13063
>             Project: Jenkins
>          Issue Type: Bug
>          Components: junit
>            Reporter: Philip Corlatan
>
> We are using the option "Publish test results" for all our build jobs
> and are specifiying the following pattern for "Test results in XML format:"
> "\_test/results/TEST\_*.xml"
> When our ant build script is completed, there are the following files 
> available matching this pattern:
> _test/results/TEST_hmm.xml
> _test/results/TEST_mssql2008.xml
> _test/results/TEST_oracle11g.xml
> _test/results/TESTS-TestSuites
> Since we updated to Jenkins 1.454, the file 
> "_test/results/TEST_oracle11g.xml" will not be included anymore in the 
> resulting test report (JOB/builds/TIMESTAMP/junitResult.xml) for all our 
> builds.
> Only "TEST_hmm.xml" and "TEST_mssql2008.xml" are considered.
> Symptoms:
> - The build succeeds even if some of our Oracle tests fail
> - The test result trend graph shows the wrong number of test
> The listed files are all available in the specified directory and the HTML 
> test report, which we create additionally, includes all test results.
> An update to Jenkins 1.455 did not help.
> Please let me know if you need any further information.

--
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

        

Reply via email to