-
Notifications
You must be signed in to change notification settings - Fork 55
Description
I found a coverage build apparently hung (http://build.willowgarage.com/job/ros-latest-all-covtest-ubuntu-hardy-x86/2/), with the following culprit processes:
{{{
wgsim 17076 0.0 0.0 1972 824 ? S 07:35 0:00 make -f CMakeFiles/pyunit_test_test_classes.py.dir/build.make CMakeFiles/pyunit_test_test_classes.py.dir/build
wgsim 17077 0.0 0.0 1772 484 ? S 07:35 0:00 /bin/sh -c cd /home/wgsim/workspace/ros-latest-all-covtest-ubuntu-hardy-x86/ros-pkg/pr2_robot/pr2_camera_synchronizer && python test/test_classes.py --cov --gtest_output=xml:/home/wgsim/workspace/ros-latest-all-covtest-ubuntu-hardy-x86/ros/test/test_results/pr2_camera_synchronizer/test_test_classes.py.xml
wgsim 17078 0.0 0.3 22528 10860 ? Sl 07:35 0:00 python test/test_classes.py --cov --gtest_output=xml:/home/wgsim/workspace/ros-latest-all-covtest-ubuntu-hardy-x86/ros/test/test_results/pr2_camera_synchronizer/test_test_classes.py.xml
}}}
Killing 17078 (the pyunit test) allowed the build to proceed.
I'm unable to replicate this on my own machine, and it didn't hang on the previous iteration of the coverage build (http://build.willowgarage.com/job/ros-latest-all-covtest-ubuntu-hardy-x86/1/).
This build uses Bullseye's wrappers, but that doesn't seem relevant because this package doesn't seem to do any compiling. More likely relevant is the --cov argument that's being passed to Python to turn on Python's coverage module.
Not sure how to track this down.
I'll note that https://code.ros.org/trac/ros/ticket/1629 would prevent the hang, mostly making this problem much less serious.
trac data:
- Owner: blaise
- Reporter: gerkey
- Reported at: Tue Apr 20 10:49:57 2010
- URL: https://code.ros.org/trac/wg-ros-pkg/ticket/4222