inject classname for gtest result files

[dirk-thomas]

Sadly gtest doesn't offer a way to customize the classname attribute which is used by Jenkins xunit to create the hierarchy. Therefore I chose to modify the generated gtest result files.

Before the gtest results were under the (root) entry with no indication to the package: http://ci.ros2.org/job/ci_linux/3531/testReport/(root)/

After they are under an entry names after the package: http://ci.ros2.org/job/ci_linux/3540/testReport/ament_index_cpp/

• Linux
• Linux-aarch64
• macOS
• Windows

[mikaelarguedas]

code change lgtm, looking forward for green CI with the test results with the new hierarchy

[mikaelarguedas]

Looks good,

Some gtests seem to not be impacted:
http://ci.ros2.org/job/ci_linux/3541/testReport/(root)/projectroot/class_loader_fviz_test/
http://ci.ros2.org/job/ci_linux/ws/ws/build/class_loader/test_results/class_loader/class_loader_fviz_test.gtest.xml

[dirk-thomas]

All results reported under (root)/projectroot are coming from CTest directly. That means the relevant xUnit result files are in the package build folder under Testing/<timestamp>. We currently don't touch these result files at all.

gtest itself will also generate a result file, the one you referenced: build/class_loader/test_results/class_loader/class_loader_fviz_test.gtest.xml. The content of that is:

<?xml version="1.0" encoding="UTF-8"?>
<testsuites tests="1" failures="0" disabled="0" errors="0" timestamp="2017-11-15T22:13:34" time="0.001" name="AllTests">
  <testsuite name="FvizTest" tests="1" failures="0" disabled="0" errors="0" time="0.001">
    <testcase name="basic_test" status="run" time="0.001" classname="class_loader.FvizTest" />
  </testsuite>
</testsuites>

The classname attribute has been prepended with the package name class_loader.. Therefore you will find a class_loader item in the main test result page (http://ci.ros2.org/job/ci_linux/3541/testReport/). Without this patch the test was reported under (root)/FvizTest (e.g. http://ci.ros2.org/view/nightly/job/nightly_linux_debug/647/testReport/(root)/FvizTest/).

[mikaelarguedas]

xUnit result files are in the package build folder under Testing/. We currently don't touch these result files at all.

Ok that's the part I missed. Thanks for clarifying

Therefore you will find a class_loader item in the main test result page (http://ci.ros2.org/job/ci_linux/3541/testReport/).

Yeah as it happens quite often recently I was unable to open the class_loader folder on the main page so I looked into the one in (root)/projectroot. Are you able to display http://ci.ros2.org/job/ci_linux/3541/testReport/class_loader/ ?

[dirk-thomas]

I get the feeling that the problem is related to follow up builds. I created a separate job and there it works fine again: http://ci.ros2.org/view/All/job/dirk_ci_linux/1/testReport/class_loader/

Maybe Jenkins has a problem to open the test results from previous builds if newer builds have been triggered or are ongoing?