Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[test] individualMarkersNoKinect node fails to write test result into xml #40

Open
130s opened this issue Jun 14, 2017 · 1 comment
Open

Comments

@130s
Copy link
Member

130s commented Jun 14, 2017

Originally found in #39

Got a hint from an answer, what seems to be happening is:

Issue description

  1. Testcases are running and passing.
  2. 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
  1. 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.

@130s
Copy link
Member Author

130s commented Jun 15, 2017

Looking at the full log, this error only occurs with individualMarkersNoKinect node.

Maybe only because all the tests currently in use use individualMarkersNoKinect #16?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant