Ask Your Question

Examine ROS buildfarm pull request testing result output

asked 2016-07-27 21:12:25 -0600

130s gravatar image

updated 2016-07-27 21:30:51 -0600

I particularly have no clue in how to analyze the result of pull request testing on ROS buildfarm.

A test on buildfarm for one of my PRs fails, while the tests in the repo run on Travis CI succeeds. Same result (good on Travis, failure on buildfarm) keeps happening with updated commits so the behavior seems stable. And on buildfarm, tests defined in the package seems to be passing too. Not sure what makes the buildfarm script to fail the test.

Can anyone tell us what to look for when the job fails for PR testing on buildfarm?

I typically try to find keywords "fail", "error", "not found", "summary", "undefined" (to hit rostest result section) by in-page search. For the buildfarm output I also browsed through. For the particular aforementioned PR, however, none of these didn't convince me for the cause of the error.


edit retag flag offensive close merge delete

1 Answer

Sort by » oldest newest most voted

answered 2016-07-27 21:41:34 -0600

tfoote gravatar image

updated 2016-07-27 21:42:49 -0600

Looking at the build log it appears to pass the tests, but the conversion to JUnit xml format fails when Jenkins is parsing the results. And the error appears to be due to a missing xml file. Looking at the last file processed it appears that the output has no test results,

The file in question: rosunit-nxo_moveit.xml appears to have no results inside it.

<?xml version="1.0" encoding="utf-8"?>

Looking at the full log it appears that there should be one successful test in the xml.

Erroring section of the log:

Clean up to save disk space on slaves
18:31:13 + rm -fr catkin_workspace/build_isolated
18:31:13 + rm -fr catkin_workspace/devel_isolated
18:31:13 + rm -fr catkin_workspace/install_isolated
18:31:13 + echo # END SECTION
18:31:13 # END SECTION
18:31:13 [WARNINGS]Parsing warnings in console log with parser GNU C Compiler 4 (gcc)
18:31:13 [WARNINGS]Computing warning deltas based on reference build #2
18:31:13 [xUnit] [INFO] - Starting to record.
18:31:13 [xUnit] [INFO] - Processing GoogleTest-1.6
18:31:13 [xUnit] [INFO] - [GoogleTest-1.6] - 11 test report file(s) were found with the pattern 'catkin_workspace/test_results/**/*.xml' relative to '/home/jenkins-slave/workspace/Ipr__rtmros_nextage__ubuntu_trusty_amd64' for the testing framework 'GoogleTest-1.6'.
18:31:13 [xUnit] [INFO] - Converting '/home/jenkins-slave/workspace/Ipr__rtmros_nextage__ubuntu_trusty_amd64/catkin_workspace/test_results/nextage_gazebo/rostest-test_gz.xml' .
18:31:13 [xUnit] [INFO] - Converting '/home/jenkins-slave/workspace/Ipr__rtmros_nextage__ubuntu_trusty_amd64/catkin_workspace/test_results/nextage_gazebo/rosunit-test_gz.xml' .
18:31:13 [xUnit] [INFO] - Converting '/home/jenkins-slave/workspace/Ipr__rtmros_nextage__ubuntu_trusty_amd64/catkin_workspace/test_results/nextage_moveit_config/rostest-test_joy.xml' .
18:31:13 [xUnit] [INFO] - Converting '/home/jenkins-slave/workspace/Ipr__rtmros_nextage__ubuntu_trusty_amd64/catkin_workspace/test_results/nextage_moveit_config/rostest-test_nxo_moveit.xml' .
18:31:13 [xUnit] [INFO] - Converting '/home/jenkins-slave/workspace/Ipr__rtmros_nextage__ubuntu_trusty_amd64/catkin_workspace/test_results/nextage_moveit_config/rosunit-hz_moveplan_joy.xml' .
18:31:13 [xUnit] [INFO] - Converting '/home/jenkins-slave/workspace/Ipr__rtmros_nextage__ubuntu_trusty_amd64/catkin_workspace/test_results/nextage_moveit_config/rosunit-nxo_moveit.xml' .
18:31:13 [xUnit] [ERROR] - Conversion error Error to convert - A file not found
18:31:13 ERROR: Step ‘Publish xUnit test result report’ aborted due to exception: 
18:31:13 remote file operation failed: /home/jenkins-slave/workspace/Ipr__rtmros_nextage__ubuntu_trusty_amd64 at hudson.util.IOException2: There are some problems during the conversion into JUnit reports: 
18:31:13    at hudson.FilePath.act(
18:31:13    at hudson.FilePath.act(
18:31:13    at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(
18:31:13    at org.jenkinsci.plugins.xunit.XUnitProcessor.performXUnit(
18:31:13    at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(
18:31:13    at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(
18:31:13    at hudson.tasks.BuildStepMonitor$1.perform(
18:31:13    at hudson.model.AbstractBuild$AbstractBuildExecution.perform(
18:31:13    at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(
18:31:13    at hudson.model.Build$BuildExecution.post2(
18:31:13    at hudson.model.AbstractBuild$
18:31:13 ...
edit flag offensive delete link more


Indeed, there seems to be an issue with a mentioned test (test_nxo_moveit) that somehow quietly finishes without emitting errors. Thank you.

130s gravatar image 130s  ( 2016-07-28 13:31:54 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2016-07-27 21:12:25 -0600

Seen: 95 times

Last updated: Jul 27 '16