Skip to content

ci: QoS matching on Humble does not work in CI #359

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.

Sign up for GitHub

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

Jump to bottom
Open
maciejmajek opened this issue Jan 8, 2025 · 0 comments
Open

ci: QoS matching on Humble does not work in CI #359

maciejmajek opened this issue Jan 8, 2025 · 0 comments
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed priority/minor Lower-priority tasks that can be picked up when time allows or planned for later.

Comments

@maciejmajek
Copy link
Member

Describe the bug
For some reason, the CI (pytest) fails on tests/messages/test_transport.py (introduced in #353) fails on ROS 2 Humble. Problem could not be reproduced on two different Ubuntu 22.04 systems (one used, one fresh).

To Reproduce
Create a new branch, revert a0779e5, create PR to run CI.

Expected behavior
The test should pass the same way it passes on standard systems.

Platform

  • OS: Ubuntu 22.04
  • ROS 2 Humble

Version
#353

Additional context
None
@maciejmajek maciejmajek added bug Something isn't working good first issue Good for newcomers labels Jan 8, 2025
@maciejmajek maciejmajek added priority/minor Lower-priority tasks that can be picked up when time allows or planned for later. help wanted Extra attention is needed labels Apr 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed priority/minor Lower-priority tasks that can be picked up when time allows or planned for later.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@maciejmajek