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

Update router and session config #396

Merged
merged 2 commits into from
Jan 12, 2025
Merged

Conversation

evshary
Copy link
Contributor

@evshary evshary commented Jan 9, 2025

The default Zenoh configuration has been changed a little bit.
Let's have the sync. It helps when we need to do a comparison.

@Yadunund
Copy link
Member

Yadunund commented Jan 9, 2025

@evshary thanks for the PR. Do you mind running tests across rcl, rcl_lifecycle, rcl_action, test_communication, test_quality_of_service, rclcpp, rclcpp_components, rclcpp_lifecycle, rclcpp_action, and rclpy and reporting on the results? Just want to make sure the changes here don't cause any regressions (unlikely).

@evshary
Copy link
Contributor Author

evshary commented Jan 9, 2025

Sure. Those are the results on my local machine

  • rclcpp_lifecycle: 6 - test_lifecycle_node (Failed)
  • rclc_parameter: 1 - rclc_parameter_test (Failed)
  • rclcpp: 44 - test_node_interfaces__node_graph (Failed)
  • rclcpp: 86 - test_time (Timeout)
  • rclcpp_action: 1 - test_client (Failed)

@Yadunund
Copy link
Member

Yadunund commented Jan 9, 2025

Sure. Those are the results on my local machine

  • rclcpp_lifecycle: 6 - test_lifecycle_node (Failed)
  • rclc_parameter: 1 - rclc_parameter_test (Failed)
  • rclcpp: 44 - test_node_interfaces__node_graph (Failed)
  • rclcpp: 86 - test_time (Timeout)
  • rclcpp_action: 1 - test_client (Failed)

Hmm this is a bit concerning given that the only test that was failing before was rclcpp_action/test_client.

@evshary
Copy link
Contributor Author

evshary commented Jan 9, 2025

I'm not sure but some seem to be flaky on my side
2nd time:

  • rclc_parameter: 1 - rclc_parameter_test (Failed)
  • rclcpp: 23 - test_clock (Failed)
  • rclcpp: 86 - test_time (Timeout)
  • rclcpp_action: 1 - test_client (Failed)

BTW, I just found that I was using the latest rolling binary. Will switch to your repos file and test again.

@evshary
Copy link
Contributor Author

evshary commented Jan 9, 2025

Okay, let me summarize the result:

The errors always happen

  • rclc_parameter: 1 - rclc_parameter_test (Failed)
  • rclcpp_action: 1 - test_client (Failed)

Flaky one:

  • rclcpp_lifecycle: 6 - test_lifecycle_node (Failed)
  • rclcpp: 44 - test_node_interfaces__node_graph (Failed)
  • test_rclcpp: 65 - test_n_nodes__rmw_zenoh_cpp (Failed)

As for these two errors, they are affected by test_client and will not appear if we disable test_client, so we can ignore them (Thanks for the info from @YuanYuYuan)

  • rclcpp: 23 - test_clock (Failed)
  • rclcpp: 86 - test_time (Timeout)

Copy link
Member

@Yadunund Yadunund left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I synced with latest rolling and ran the same tests. Apart from rclcpp_action/test_client which is a known issue, the only other flaky test was test_rclcpp/test_n_nodes__rmw_zenoh_cpp which can be reproduced even on rolling if run enough times. In my experience adding --retest-until-fail 10 helps us see the failure.

colcon test --packages-select test_rclcpp --ctest-args -R test_n_nodes --event-handlers console_direct+ --retest-until-fail 10

@Yadunund Yadunund merged commit 3739a0f into ros2:rolling Jan 12, 2025
5 checks passed
@Yadunund
Copy link
Member

@Mergifyio backport jazzy humble

Copy link

mergify bot commented Jan 12, 2025

backport jazzy humble

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Jan 12, 2025
Signed-off-by: ChenYing Kuo <[email protected]>
Co-authored-by: Yadunund <[email protected]>
(cherry picked from commit 3739a0f)
mergify bot pushed a commit that referenced this pull request Jan 12, 2025
Signed-off-by: ChenYing Kuo <[email protected]>
Co-authored-by: Yadunund <[email protected]>
(cherry picked from commit 3739a0f)
@evshary evshary deleted the sync_config branch January 12, 2025 03:05
Yadunund pushed a commit that referenced this pull request Jan 13, 2025
Signed-off-by: ChenYing Kuo <[email protected]>
Co-authored-by: Yadunund <[email protected]>
(cherry picked from commit 3739a0f)

Co-authored-by: ChenYing Kuo (CY) <[email protected]>
Yadunund pushed a commit that referenced this pull request Jan 13, 2025
Signed-off-by: ChenYing Kuo <[email protected]>
Co-authored-by: Yadunund <[email protected]>
(cherry picked from commit 3739a0f)

Co-authored-by: ChenYing Kuo (CY) <[email protected]>
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.

2 participants