Ogre 1.9: gz tool test failures

[osrf-migration]

Original report (archived issue) by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).

---

While testing pull request #1354 with libogre-1.9-dev on trusty, I've observed some odd test failures of the gz tool.

UNIT_gz_TEST hangs:

$ tools/UNIT_gz_TEST
[==========] Running 9 tests from 1 test case.
[----------] Global test environment set-up.
[----------] 9 tests from gzTest
[ RUN      ] gzTest.Alive
[       OK ] gzTest.Alive (129 ms)
[ RUN      ] gzTest.Joint
[Msg] Waiting for master.
[Msg] Connected to gazebo master @ http://127.0.0.1:11345
[Msg] Publicized address: 172.23.2.90
[Err] [Node.cc:98] No namespace found
^C^\^C

PERFORMANCE_gz_stress also fails.

$ test/performance/PERFORMANCE_gz_stress 
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from gzTest
[ RUN      ] gzTest.Stress
[Msg] Waiting for master.
[Msg] Connected to gazebo master @ http://127.0.0.1:11345
[Msg] Publicized address: 172.23.2.90
[Err] [Node.cc:98] No namespace found
/home/scpeters/ws/gazebo_simbody/src/gazebo/test/performance/gz_stress.cc:95: Failure
Expected: (iters) < (20), actual: 20 vs 20
/home/scpeters/ws/gazebo_simbody/src/gazebo/test/performance/gz_stress.cc:96: Failure
Value of: !g_msgDebugOut.empty()
  Actual: false
Expected: true
/home/scpeters/ws/gazebo_simbody/src/gazebo/test/performance/gz_stress.cc:159: Failure
Value of: msg.DebugString()
  Actual: "reset {\n  time_only: true\n}\n"
Expected: g_msgDebugOut
Which is: ""
[  FAILED  ] gzTest.Stress (27935 ms)
[----------] 1 test from gzTest (27935 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (27935 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] gzTest.Stress

 1 FAILED TEST
PERFORMANCE_gz_stress: /usr/include/boost/thread/pthread/recursive_mutex.hpp:110: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.
Aborted (core dumped)

[osrf-migration]

Original comment by Jose Luis Rivero (Bitbucket: Jose Luis Rivero, GitHub: j-rivero).

---

I'm not able to reproduce this on my system.

Maybe you have a different version of gazebo installed and the test is using gz from the system?

[osrf-migration]

Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).

---

I just tried again, making sure to uninstall gazebo4 and verifying that the gz command was not found in /usr/bin. I still get the same test failure.

[osrf-migration]

Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).

---

• changed state from "new" to "on hold"

hard to reproduce, re-open if it persists

[osrf-migration]

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).

---

• set version to "all"