On Wed, Nov 7, 2012 at 12:56 PM, Wim Meeussen wrote: > Hi Daniel, > > > What shape are prereleases in for groovy? I noticed the default method is > > still going through the old server, where everything I have generates > errors > > similar to the following: > > > For Groovy there are two separate pipelines for prerelease tests. > There is the original pipeline for non-catking (dry) stacks, and a new > pipeline for catkinized (wet) repositories. Both pipelines are > accessible through the same web interface at > . > > While the new catkin-based prerelease tests are up and running, there > are a number of regressions with the original tests. We're actively > working on a fix right now, and hopefully I'll be able to push out a > working version very soon. > I tried this today on Jenkins with two very simple dry stacks. They both failed several tests with the same error: make[4]: Entering directory `/tmp/install_dir/stack_overlay/unique_identifier/unique_id/build' /tmp/install_dir/stack_overlay/unique_identifier/unique_id/bin/test_unique_id: error while loading shared libraries: libgtest.so: cannot open shared object file: No such file or directory [ROSUNIT] Outputting test results to /tmp/ros/test_results/stack_overlay_run_0/unique_id/rostest-test_unique_id.xml runTest ... FAILURE! FAILURE: test [test_unique_id] did not generate test results File "/usr/lib/python2.7/unittest/case.py", line 327, in run testMethod() File "/opt/ros/groovy/lib/python2.7/dist-packages/rosunit/baretest.py", line 167, in runTest self.assert_(os.path.isfile(test_file), "test [%s] did not generate test results"%test_name) File "/usr/lib/python2.7/unittest/case.py", line 420, in assertTrue raise self.failureException(msg) -------------------------------------------------------------------------------- [ROSUNIT]----------------------------------------------------------------------- [runTest][failed] The libgtest-dev package did get installed. Here is the full console output: http://build.willowgarage.com/job/prerelease_groovy_unique_identifier_precise_amd64/1/console Any suggestions? I use rosbuild_add_gtest() in the CMakeLists.txt, and those tests should run cleanly. -- joq