Skip to content

Attempt to reproduce intermittent unit test failures with a different DDS vendor #366

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

Closed
maspe36 opened this issue Mar 12, 2024 · 1 comment

Comments

@maspe36
Copy link
Collaborator

maspe36 commented Mar 12, 2024

As discussed in the March 11th monthly meetup, we have some occasional unit test failures. These failures have seemingly been narrowed down to rclrs_tests and appear to be related to DDS usage. See #364 for more details.

With that in mind, it is imperative that we take multiple approaches to thoroughly investigate and analyze the root causes of these failures.

For this issue, we agreed that it would be beneficial to see if we can reproduce this issue with another DDS vendor. It is not out of the question that our usage is manifesting a bug in a specific DDS implementation. Lets try as many tier 1 DDS vendors as we can get our hands on.

@maspe36
Copy link
Collaborator Author

maspe36 commented Mar 20, 2024

Ever since #372 got merged, I haven't been seeing the intermittent failures in graph_tests with Eclipse Cyclone, FastDDS, or RTI Connext.

Going to close this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant