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

Topic remap test is failing regularly #455

Closed
Karsten1987 opened this issue Jul 8, 2020 · 0 comments · Fixed by #456
Closed

Topic remap test is failing regularly #455

Karsten1987 opened this issue Jul 8, 2020 · 0 comments · Fixed by #456
Assignees
Labels
bug Something isn't working

Comments

@Karsten1987
Copy link
Collaborator

The topic remapping test is failing regularly on CI due to timeouts, e.g.:

02:07:44 22: Running main() from gmock_main.cc
02:07:44 22: [==========] Running 1 test from 1 test case.
02:07:44 22: [----------] Global test environment set-up.
02:07:44 22: [----------] 1 test from RosBag2PlayTestFixture
02:07:44 22: [ RUN      ] RosBag2PlayTestFixture.recorded_message_is_played_on_remapped_topic
02:08:44 1/1 Test #22: test_play_topic_remap__rmw_fastrtps_cpp ...***Timeout  60.10 sec
02:08:44 
02:08:44 0% tests passed, 1 tests failed out of 1
02:08:44 
02:08:44 Label Time Summary:
02:08:44 gmock    =  60.10 sec*proc (1 test)
02:08:44 
02:08:44 Total Test time (real) =  60.11 sec
02:08:44 
02:08:44 The following tests FAILED:
02:08:44 	 22 - test_play_topic_remap__rmw_fastrtps_cpp (Timeout)
02:08:44 Errors while running CTest
02:08:44 

https://ci.ros2.org/view/nightly/job/nightly_osx_extra_rmw_release/831/consoleFull#console-section-43

The problem is as usual a indeterministic execution of ROS2, which doesn't allow to verify an exact number of messages being transported.

@Karsten1987 Karsten1987 added the bug Something isn't working label Jul 8, 2020
@Karsten1987 Karsten1987 self-assigned this Jul 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant