-
Notifications
You must be signed in to change notification settings - Fork 0
Connext: Automatic participant index failed to initialize #93
Comments
I asked on for details on the connext forum: https://community.rti.com/forum-topic/please-verify-constistent-transport-discovery-configuration |
This is still an issue, though it has low probability. It can interfere with testing of flaky tests where we're repeating many times (e.g. it failed on repeat 417 in this flakiness-testing build: https://ci.ros2.org/job/ci_linux/4085). The response on the forum was:
Setting the participant ID manually isn't really viable even if it's do-able for tests. This should be resolved for users that want automatic participant ID selection. @ros2/team Is anyone aware of issues that would impact the interface availability in the docker containers? Is there something we can improve there, or -- given that the interface is fine for all other runs of the tests -- is this more likely an issue in how connext is working with the interface? |
I asked for specifics on what changed between connext versions but haven't heard back: https://community.rti.com/forum-topic/please-verify-constistent-transport-discovery-configuration |
Since we haven't seen this for quite a while I will go ahead and close the ticket for now. |
https://ci.ros2.org/view/nightly/job/nightly_linux_repeated/957/testReport/junit/(root)/projectroot/test_tlsf__rmw_connext_cpp/
This post says it's from a network interface configuration issue.
Failed on repeat 12 and there have been CI jobs not showing this error since then so it seems like bad luck.
The text was updated successfully, but these errors were encountered: