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

tests: randomize ROS_DOMAIN_ID for tests that need it #144

Closed
wants to merge 1 commit into from

Conversation

kyrofa
Copy link
Member

@kyrofa kyrofa commented Jul 10, 2019

The test_generate_policy_no_nodes test appears flaky under Windows. It assumes the default DDS domain is empty of nodes, which may not always be the case. This PR attempts to fix #143 by randomizing the domain ID for that test.

The `test_generate_policy_no_nodes` test appears flaky under Windows. It
assumes the default DDS domain is empty of nodes, which may not always
be the case. Randomize the domain ID for that test.

Fix ros2#143

Signed-off-by: Kyle Fazzari <[email protected]>
@nuclearsandwich
Copy link
Member

We can't randomize the domain ID on our current infrastructure and have the test work across all platforms. Our current Windows and Mac hosts share a network and can inadvertently communicate with each other during tests if using the same domain ids.

@kyrofa
Copy link
Member Author

kyrofa commented Jul 10, 2019

Alright, thanks @nuclearsandwich, we can scratch this attempt. It was a bit of a hack anyway-- this is sounding more like a zombie node from another test, perhaps.

@kyrofa kyrofa closed this Jul 10, 2019
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

Successfully merging this pull request may close these issues.

test_generate_policy fails on Windows
2 participants