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

SEGFAULT on CTest should be reported

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Minor Minor
    • xunit-plugin
    • None

      When a CTest fails on a segfault, xUnit reports this as a failure, but in the Stack Trace, doesn't show that it failed because of a segfault. GTest shows that it PASSED, which our logs show that as well, but behind the scenes, xUnit must know that it segfaulted as well to put it into the Failed Test section. The exit code of the test shows that it is a SEGFAULT as well. Was hoping to have some sort of indication that a test failed because of a SEGFAULT displayed in the xUnit failed test results.

        1. Segfault_Unit_Test_xunit.png
          Segfault_Unit_Test_xunit.png
          21 kB
        2. image-2021-10-07-14-51-56-270.png
          image-2021-10-07-14-51-56-270.png
          107 kB
        3. image-2021-10-07-14-51-47-177.png
          image-2021-10-07-14-51-47-177.png
          107 kB
        4. xUnitExample.xml
          3 kB
        5. segfault.png
          segfault.png
          5 kB

          [JENKINS-66695] SEGFAULT on CTest should be reported

          David created issue -

          Nikolas Falco added a comment -

          I need a complete xml test report (produced by CTest) so I can look into and prepare an appropriate xlst to generate a failure case

          Nikolas Falco added a comment - I need a complete xml test report (produced by CTest) so I can look into and prepare an appropriate xlst to generate a failure case
          David made changes -
          Attachment New: xUnitExample.xml [ 56333 ]

          David added a comment -

          I've attached an XML that contains only the test that I am talking about. Two tests in my repo show this same behavior though, with possible others throughout my project.

          David added a comment - I've attached an XML that contains only the test that I am talking about. Two tests in my repo show this same behavior though, with possible others throughout my project.

          David added a comment - - edited

          Is there any status on this. Do you need any more info than what I have provided?

          David added a comment - - edited Is there any status on this. Do you need any more info than what I have provided?

          Nikolas Falco added a comment -

          no movement on this. I have all informations thanks

          Nikolas Falco added a comment - no movement on this. I have all informations thanks
          Nikolas Falco made changes -
          Summary Original: Segfault Test Should Report as Failed New: Segfault on CTest Test Should Report as Failed
          Nikolas Falco made changes -
          Summary Original: Segfault on CTest Test Should Report as Failed New: SEGFAULT on CTest should be reported

          Nikolas Falco added a comment - - edited

          The output you attach is about CTest I do not know why in the description you mention GTest. In xUnit there are GoogleTest and GTester which formats are completly different.
          Anyway to show the Exit Code value implies change actual format (before failure = system-out).

          <?xml version="1.0" encoding="UTF-8"?>
<testsuites xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xunit="http://www.xunit.org">
   <testsuite name="CTest"
              tests="1"
              time="88.000"
              failures="1"
              errors="0"
              skipped="0">
      <testcase classname="projectroot.tests" name="test1.realStdin" time="0.025">
         <failure>SEGFAULT</failure>
         <system-out><![CDATA[Running main() from /home/user/googletest-release-1.10.0/googletest/src/gtest_main.cc
Note: Google Test filter = test1.realStdin
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from StdinComponent
[ RUN      ] test1.realStdin
[       OK ] test1.realStdin (1 ms)
[----------] 1 test from StdinComponent (1 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (1 ms total)
[  PASSED  ] 1 test.
]]></system-out>
      </testcase>
   </testsuite>
</testsuites>

          I do not know if report SEGFAULT as error instead of failure and if there are other possible values as Exit Code that will complicate the way to understand what is error and what failure

          Nikolas Falco added a comment - - edited The output you attach is about CTest I do not know why in the description you mention GTest. In xUnit there are GoogleTest and GTester which formats are completly different. Anyway to show the Exit Code value implies change actual format (before failure = system-out). <?xml version= "1.0" encoding= "UTF-8" ?> <testsuites xmlns:xs = "http://www.w3.org/2001/XMLSchema" xmlns:xunit = "http://www.xunit.org" > <testsuite name= "CTest" tests= "1" time= "88.000" failures= "1" errors= "0" skipped= "0" > <testcase classname= "projectroot.tests" name= "test1.realStdin" time= "0.025" > <failure> SEGFAULT </failure> <system-out> <![CDATA[Running main() from /home/user/googletest-release-1.10.0/googletest/src/gtest_main.cc Note: Google Test filter = test1.realStdin [==========] Running 1 test from 1 test suite. [----------] Global test environment set-up. [----------] 1 test from StdinComponent [ RUN ] test1.realStdin [ OK ] test1.realStdin (1 ms) [----------] 1 test from StdinComponent (1 ms total) [----------] Global test environment tear-down [==========] 1 test from 1 test suite ran. (1 ms total) [ PASSED ] 1 test. ]]> </system-out> </testcase> </testsuite> </testsuites> I do not know if report SEGFAULT as error instead of failure and if there are other possible values as Exit Code that will complicate the way to understand what is error and what failure
          Nikolas Falco made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

            nfalco Nikolas Falco
            venn David
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: