Generate xunit files valid for the junit10.xsd#220
Conversation
Signed-off-by: Jose Luis Rivero <jrivero@osrfoundation.org>
Should this be updated then to signal an |
In the case of detecting segfaults or other problems not related to bad results of the test I think so. Let's follow this here: ament/ament_cmake#225 |
Signed-off-by: Jose Luis Rivero <jrivero@osrfoundation.org>
Signed-off-by: Jose Luis Rivero <jrivero@osrfoundation.org>
* Generate xunit files valid for the junit10.xsd (#220) Signed-off-by: Jose Luis Rivero <jrivero@osrfoundation.org> * remove status attribute from result XML (#212) Signed-off-by: Dirk Thomas <dirk-thomas@users.noreply.github.com> Co-authored-by: Jose Luis Rivero <jrivero@osrfoundation.org> Co-authored-by: Dirk Thomas <dirk-thomas@users.noreply.github.com>
* Generate xunit files valid for the junit10.xsd (#220) Signed-off-by: Jose Luis Rivero <jrivero@osrfoundation.org> * remove status attribute from result XML (#212) Signed-off-by: Dirk Thomas <dirk-thomas@users.noreply.github.com> Co-authored-by: Jose Luis Rivero <jrivero@osrfoundation.org> Co-authored-by: Dirk Thomas <dirk-thomas@users.noreply.github.com>
Signed-off-by: Jose Luis Rivero <jrivero@osrfoundation.org>
With the new xunit plugin version 2.x the xunit files generated should be compliant with the junit10.xsd.
The current code in different packages writing xunit files lacks the required attribute
errorsand useskippedinstead ofskip. For theskipattribute the change is trivial. For theerrorsattribute the description is:The code of linters in this repository exit the test to the system if it founds some problems with the manipulation of the different tools (like the lack of cppcheck in ament_cppcheck) so I'm assuming here that if the test is not aborted before the number of these
errorsis 0.Locally the files can be validated using (download the xsd from the link above):
xmllint --schema junit-10.xsd path/to/ppcheck.xunit.xml --nooutWaiting the buildfarm test for this job: