[test] individualMarkersNoKinect node fails to write test result into xml
130s opened this issue · comments
Originally found in #39
Got a hint from an answer, what seems to be happening is:
Issue description
- Testcases are running and passing.
- A testcase failed writing results into xml. The process of writing into file teminates and leaves the file content in incomplete form. But testcase process goes on.
12:02:31 /opt/ros/lunar/share/rostest/cmake/../../../bin/rostest --pkgdir=/tmp/catkin_workspace/src/ar_track_alvar/ar_track_alvar --package=ar_track_alvar --results-filename test_marker_arg_config-basic.xml --results-base-dir /tmp/catkin_workspace/test_results /tmp/catkin_workspace/src/ar_track_alvar/ar_track_alvar/test/marker_arg_config-basic.test
12:02:31 ... logging to /home/buildfarm/.ros/log/rostest-5e93fb8bd950-1650.log
12:02:31 [ROSUNIT] Outputting test results to /tmp/catkin_workspace/test_results/ar_track_alvar/rostest-test_marker_arg_config-basic.xml
12:02:34 individualMarkersNoKinect: /usr/include/boost/thread/pthread/recursive_mutex.hpp:113: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.
12:02:34 �[33m[ WARN] [1497294151.766305652]: Command line arguments are deprecated. Consider using ROS parameters and remappings.�[0m
- On ROS buildfarm, test result xmls are reviewed at the end, where the job fails because the file content is incomplete.
Looking at the full log, this error only occurs with individualMarkersNoKinect node.
Environment, How to reproduce
Any pull request against this repo would face this issue without fix.
You should be able to replicate the issue trying to look into the test result xml but I don't know the exact steps to do that.