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

test_logging_rosout test failing on macOS #792

Closed
azeey opened this issue Sep 4, 2020 · 3 comments · Fixed by #846
Closed

test_logging_rosout test failing on macOS #792

azeey opened this issue Sep 4, 2020 · 3 comments · Fixed by #846
Assignees
Labels
bug Something isn't working

Comments

@azeey
Copy link

azeey commented Sep 4, 2020

Bug report

Required Info:

  • Operating System:
    • macOS Mojave
  • Installation type:
    • source
  • Version or commit hash:
    • master since 2020-09-03
  • DDS implementation:
    • RTI Connext

Steps to reproduce issue

The test TestLoggingRosoutWithDifferentSettings is failing on macOS repeated CI with the following log

[ RUN      ] TestLoggingRosoutWithDifferentSettings/TestLoggingRosoutFixture__rmw_connext_cpp.test_logging_rosout/test_enable_explicit_global_rosout_enable_node_option
[INFO] [1599124760.684844240] [ns.test_rcl_node_logging_rosout]: SOMETHING
/Users/osrf/jenkins-agent/workspace/nightly_osx_repeated/ws/src/ros2/rcl/rcl/test/rcl/test_logging_rosout.cpp:190: Failure
Expected equality of these values:
  success
    Which is: false
  GetParam().expected_success
    Which is: true
[  FAILED  ] TestLoggingRosoutWithDifferentSettings/TestLoggingRosoutFixture__rmw_connext_cpp.test_logging_rosout/test_enable_explicit_global_rosout_enable_node_option, where GetParam() = test_enable_explicit_global_rosout_enable_node_option (4331 ms)

The test history shows that this might be a flaky test.

Expected behavior

test passes

Actual behavior

test fails

@jacobperron
Copy link
Member

This hasn't occurred on my watch, but I wouldn't be surprised if it's flaky given the test depends on waiting for a subscription to be ready.

@ivanpauno ivanpauno added the bug Something isn't working label Oct 14, 2020
@ivanpauno
Copy link
Member

Connext discovery is sometimes slow, I would extend the 10 retries to 50 (max wait time goes from 1s to 5s).

@ivanpauno
Copy link
Member

ivanpauno commented Oct 28, 2020

This is still failing sometimes (eg), I will increase the number of retries to see if that makes the test less flaky.

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.

3 participants