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

[backport foxy] Add QoS decoding translation for infinite durations to RMW_DURATION_INFINITE (backport #684) #1088

Merged
merged 5 commits into from
May 26, 2023

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Sep 13, 2022

This is an automatic backport of pull request #684 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

@emersonknapp emersonknapp changed the title Add QoS decoding translation for infinite durations to RMW_DURATION_INFINITE (backport #684) [backport foxy] Add QoS decoding translation for infinite durations to RMW_DURATION_INFINITE (backport #684) Sep 13, 2022
emersonknapp and others added 2 commits September 15, 2022 13:19
…NFINITE (#684)

* Add QoS decoding translation for infinite durations to RMW_DURATION_INFINITE

Signed-off-by: Emerson Knapp <[email protected]>
(cherry picked from commit de70a81)
Signed-off-by: Emerson Knapp <[email protected]>
@emersonknapp emersonknapp self-assigned this Sep 15, 2022
@emersonknapp emersonknapp self-requested a review September 15, 2022 21:13
@emersonknapp
Copy link
Collaborator

emersonknapp commented Sep 15, 2022

Gist: https://gist.githubusercontent.com/emersonknapp/6b02a51c6326c1689d6f1745f25d064b/raw/0688bfd464a365c6b3a72397c58fc2512c2d6340/ros2.repos
BUILD args: --packages-above-and-dependencies rosbag2_transport
TEST args: --packages-above rosbag2_transport
ROS Distro: foxy
Job: ci_launcher
ci_launcher ran: https://ci.ros2.org/job/ci_launcher/10813

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Windows Build Status

Rerun on focal

  • Linux Build Status
  • Linux-aarch64 Build Status

Copy link
Contributor

@MichaelOrlov MichaelOrlov left a comment

Choose a reason for hiding this comment

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

@emersonknapp Backport looks good to me.
Only concern about CI failures on Windows

C:\ci\ws\src\ros2\rosbag2\rosbag2_tests\test\rosbag2_tests\test_rosbag2_record_end_to_end.cpp(488): error: Expected: (metadata.relative_file_paths.size()) >= (1), actual: 0 vs 1
Bagfile never split!
[  FAILED  ] RecordFixture.record_end_to_end_test_with_zstd_file_compression_compresses_files (1376 ms)

@MichaelOrlov
Copy link
Contributor

MichaelOrlov commented Sep 21, 2022

Rerun CI for Windows

  • Windows Build Status

@MichaelOrlov
Copy link
Contributor

It seems that CI Windows job failed to some glitches in infrastructure or race conditions in unit tets.
Trying to rerun CI for Windows one more time:

  • Windows Build Status

@MichaelOrlov
Copy link
Contributor

@emersonknapp It seems that TestRos2BagRecord.test_incomplete_qos_profile consistently fails on Windows CI Job.
And it looks like it somehow relates to the changes in this PR.
Can you please investigate this failure?

Signed-off-by: Emerson Knapp <[email protected]>
@emersonknapp
Copy link
Collaborator

Windows: Build Status

@MichaelOrlov
Copy link
Contributor

Gist: https://gist.githubusercontent.com/MichaelOrlov/5b6d727b8a061123e96c0c58c3839d22/raw/0688bfd464a365c6b3a72397c58fc2512c2d6340/ros2.repos
BUILD args: --packages-above-and-dependencies rosbag2_transport
TEST args: --packages-above rosbag2_transport
ROS Distro: foxy
Job: ci_launcher
ci_launcher ran: https://ci.ros2.org/job/ci_launcher/12101

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Windows Build Status

@MichaelOrlov
Copy link
Contributor

Rebuil on focal and without connext_dds
BUILD args: --packages-above-and-dependencies rosbag2_transport
TEST args: --packages-above rosbag2_transport
ROS Distro: foxy
Job: ci_launcher
ci_launcher ran: https://ci.ros2.org/job/ci_launcher/12102

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Windows Build Status

@MichaelOrlov
Copy link
Contributor

Failure in the Windows CI job in ros2bag.test.test_record_qos_profiles.test_record_qos_profiles tests is unrelated to the changes from this PR and has been investigated in #1349.

@MichaelOrlov
Copy link
Contributor

Re-run the Windows job one more time after rebase.

  • Windows Build Status

@MichaelOrlov
Copy link
Contributor

The Linux job failed from the previous CI run due to the infrastructure issue related to the java.
However, the CI launcher automatically restarted those job and it passed green * Linux Build Status

Thanks @emersonknapp for teaching me how to find an automatically restarted CI job.

@emersonknapp
Copy link
Collaborator

Maybe let's wait for #1353 and then run one more clean CI on this one - though it looks like everything is OK here.

@MichaelOrlov
Copy link
Contributor

@emersonknapp Ahh it will not be green anyway. There are a lot more warnings and random failures.
This is like a nightmare. I want to wrap it up and forget.

@MichaelOrlov MichaelOrlov merged commit b1507b6 into foxy May 26, 2023
@delete-merged-branch delete-merged-branch bot deleted the mergify/bp/foxy/pr-684 branch May 26, 2023 06:36
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.

3 participants