Skip to content
This repository has been archived by the owner on Nov 22, 2023. It is now read-only.

Failure of unittest_pilz_joint_trajectory_controller_is_executing (Travis) #429

Closed
martiniil opened this issue Jun 30, 2020 · 3 comments
Closed
Labels
bug Something isn't working

Comments

@martiniil
Copy link
Contributor

Commit

1489a9f from here: #408

Log

[ROSUNIT] Outputting test results to /root/target_ws/build/pilz_control/test_results/pilz_control/rostest-test_unittest_pilz_joint_trajectory_controller_is_executing.xml


terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::condition_error> >'


  what():  boost::condition_variable::do_wait_until failed in pthread_cond_timedwait: Invalid argument

Full log: https://travis-ci.org/github/PilzDE/pilz_robots/jobs/703499360

Some thoughts

I don't think that this is related to the changes of #408.

This is a sporadic failure. I haven't seen it locally, so far. I have no clue, which part of the code generates this failure. We are not directly using boost in pilz_control.

Google showed me this: boostorg/thread#308

@martiniil martiniil added the bug Something isn't working label Jun 30, 2020
@martiniil
Copy link
Contributor Author

@martiniil
Copy link
Contributor Author

martiniil commented Jul 23, 2020

The std::future used in the test should not be a problem. If the thread is not completed, the destructor of the future object is blocking. The result would be

RLTestTimeoutException: max time [60.0s] allotted for test

@martiniil
Copy link
Contributor Author

Did not occur for 28 days and I am not able to reproduce it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant