-
Notifications
You must be signed in to change notification settings - Fork 117
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
Avoid unnecessary sets of GUID_t #586
base: rolling
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks reasonable to me. I'll go ahead and run CI on it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MiguelCompany this PR looks good to me (using current count from dds), but i am not sure why this can fix the problem. Using GUID list based on handles, why it cannot work in the same way with this PR?
We can ignore the Windows failure; that is due to a separate issue that has since been fixed. We can rerun that later. However, there are a lot of new failures in Linux and Linux aarch64 with this PR in place. @MiguelCompany can you take a look? |
@clalancette I only tested this against the It seems After we change rolling to use Fast DDS |
@MiguelCompany Now that we have ros2/ros2#1241 merged, feel free to revise this PR to what you think it should be, or open a new one with your new approach. Then we can run CI again. |
Signed-off-by: Miguel Company <[email protected]>
Signed-off-by: Miguel Company <[email protected]>
eaa72a3
to
9d55fd7
Compare
@clalancette Thanks. I've just pushed the new approach, in which the matched counts are directly obtained from Fast DDS. |
@clalancette Sorry, I just saw this has conflicts. Will rebase tomorrow |
@MiguelCompany can you rebase this when you have time? |
While debugging the test failures on ros2/ros2#1241, I discovered we could directly keep the publisher and subscription counts instead of keeping a set of GUID_t.
This PR does just that.