Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-28871

CppTest 9.5 report file seems not valid for xUnit when no tests was executed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • xunit-plugin
    • None
    • Jenkins 1.617
      Xunit : 1.60 (same with the last one 1.96)
      CPPtest 7.3

      Hi everyone,

      I have some troubles when parsing a XML report. This report was generated by cpptestcli -report unitTests.xml.
      I can import it manually in Visual studio 2010. But the last step of the job fails.

      here is what is written on the log :

      [Cpptest] Collecting Cpptest analysis files...
      [Cpptest] Computing warning deltas based on reference build
      #1Archiving artifacts
      [xUnit] [INFO] - Starting to record.
      [xUnit] [INFO] - Processing CppTest-7.x
      [xUnit] [INFO] - [CppTest-7.x] - 2 test report file(s) were found with the pattern '.xml' relative to 'D:\Jenkins\workspace\STS_INTRFACE_TU' for the testing framework 'CppTest-7.x'.
      [xUnit] [ERROR] - The converted file for the result file 'D:\Jenkins\workspace\STS_INTRFACE_TU\unitTests.xml' (during conversion process for the metric 'CppTest') is not valid. The report file has been skipped.*
      [xUnit] [INFO] - Fail BUILD because 'set build failed if errors' option is activated.
      [xUnit] [INFO] - There are errors when processing test results.
      [xUnit] [INFO] - Skipping tests recording.
      [xUnit] [INFO] - Stop build.
      Build step 'Publish xUnit test result report' changed build result to FAILURE
      Finished: FAILURE

      I really dont know why. I have 6 projects, 3 of them fail, the 3 others are OK .
      I join you the report generated.

      Thanks a lot for your help

      Regards

        1. unitTests.xml
          18 kB
          Antoine Manceau

          [JENKINS-28871] CppTest 9.5 report file seems not valid for xUnit when no tests was executed

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Nikolas Falco
          Path:
          src/main/java/org/jenkinsci/plugins/xunit/types/CppTest.java
          src/main/java/org/jenkinsci/plugins/xunit/types/CppTestJunitHudsonTestType.java
          src/main/java/org/jenkinsci/plugins/xunit/types/CppTestUnit.java
          src/main/resources/org/jenkinsci/plugins/xunit/types/cpptestunit-2.0-to-junit-1.0.xsl
          src/main/resources/org/jenkinsci/plugins/xunit/types/model/xsd/junit-10.xsd
          src/test/java/org/jenkinsci/plugins/xunit/types/AbstractTest.java
          src/test/java/org/jenkinsci/plugins/xunit/types/CppTestTest.java
          src/test/java/org/jenkinsci/plugins/xunit/types/CppTestUnitTest.java
          src/test/java/org/jenkinsci/plugins/xunit/types/ValidInputMetricXSLTest.java
          src/test/resources/org/jenkinsci/plugins/xunit/types/cpptest/testcase1/input.xml
          src/test/resources/org/jenkinsci/plugins/xunit/types/cpptest/testcase1/result.xml
          src/test/resources/org/jenkinsci/plugins/xunit/types/cpptest/testcase2/input.xml
          src/test/resources/org/jenkinsci/plugins/xunit/types/cpptest/testcase2/result.xml
          src/test/resources/org/jenkinsci/plugins/xunit/types/cpptest/testcase3/input.xml
          src/test/resources/org/jenkinsci/plugins/xunit/types/cpptest/testcase3/result.xml
          src/test/resources/org/jenkinsci/plugins/xunit/types/cpptestunit/testcase1/inputcpptest.xml
          src/test/resources/org/jenkinsci/plugins/xunit/types/cpptestunit/testcase1/junit-result.xml
          src/test/resources/org/jenkinsci/plugins/xunit/types/cpptestunit/testcase2/report-cpptest-tests.xml
          src/test/resources/org/jenkinsci/plugins/xunit/types/cpptestunit/testcase2/result-junit.xml
          http://jenkins-ci.org/commit/xunit-plugin/cd5367f2b14ceb5430fd2c37d341da8d0ae9741c
          Log:
          JENKINS-28871 CppTest 9.5 report file seems not valid for xUnit when no tests was executed

          Improve CppTest XSL to better handle 7.x and 9.x reports. Cover also the case no test was run.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Nikolas Falco Path: src/main/java/org/jenkinsci/plugins/xunit/types/CppTest.java src/main/java/org/jenkinsci/plugins/xunit/types/CppTestJunitHudsonTestType.java src/main/java/org/jenkinsci/plugins/xunit/types/CppTestUnit.java src/main/resources/org/jenkinsci/plugins/xunit/types/cpptestunit-2.0-to-junit-1.0.xsl src/main/resources/org/jenkinsci/plugins/xunit/types/model/xsd/junit-10.xsd src/test/java/org/jenkinsci/plugins/xunit/types/AbstractTest.java src/test/java/org/jenkinsci/plugins/xunit/types/CppTestTest.java src/test/java/org/jenkinsci/plugins/xunit/types/CppTestUnitTest.java src/test/java/org/jenkinsci/plugins/xunit/types/ValidInputMetricXSLTest.java src/test/resources/org/jenkinsci/plugins/xunit/types/cpptest/testcase1/input.xml src/test/resources/org/jenkinsci/plugins/xunit/types/cpptest/testcase1/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/cpptest/testcase2/input.xml src/test/resources/org/jenkinsci/plugins/xunit/types/cpptest/testcase2/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/cpptest/testcase3/input.xml src/test/resources/org/jenkinsci/plugins/xunit/types/cpptest/testcase3/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/cpptestunit/testcase1/inputcpptest.xml src/test/resources/org/jenkinsci/plugins/xunit/types/cpptestunit/testcase1/junit-result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/cpptestunit/testcase2/report-cpptest-tests.xml src/test/resources/org/jenkinsci/plugins/xunit/types/cpptestunit/testcase2/result-junit.xml http://jenkins-ci.org/commit/xunit-plugin/cd5367f2b14ceb5430fd2c37d341da8d0ae9741c Log: JENKINS-28871 CppTest 9.5 report file seems not valid for xUnit when no tests was executed Improve CppTest XSL to better handle 7.x and 9.x reports. Cover also the case no test was run.

            nfalco Nikolas Falco
            ayer Antoine Manceau
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: