-
Notifications
You must be signed in to change notification settings - Fork 99
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
Working to bring CI back to green #1015
Conversation
I've gotten everything back to green except ROS 2 Doc Which is showing a real failure on the farm: https://build.ros2.org/view/Rdoc/job/Rdoc__rcl__ubuntu_jammy_amd64/81/console
This looks like something to do with the python transition to path objects instead of string representations of paths between something generated and exhale. |
It seems like the version being installed on CI is |
It generally works but it's not an officially supported configuration so we don't want to block CI for those cases. Especially here it's failing on a system package deprecation. ``` #22 16.62 E: Package 'python3-pytest-rerunfailures' has no installation candidate #22 ERROR: process "/bin/sh -c for i in 1 2 3; do apt-get update && apt-get install -q -y python3-pytest-rerunfailures && apt-get clean && break || if [ $i -lt 3 ]; then sleep 5; else false; fi; done" did not complete successfully: exit code: 1 ```
It will fail but it's actually broken
Merging to get CI back to mostly green with a tracker for the one remaining issue: #1029 |
Thank you! |
* drop python 2.7 no longer supported on github actions. * move to noetic and focal from melodic and bionic * pin empy to less than 4 * move from foxy to humble * focal to jammy for humble only * Use Ubuntu Noble for Rolling builds Co-authored-by: Scott K Logan <[email protected]>
It's failing with several recent changes. This PR is to just try to resolve that and unblock other changes.
I think python 2.7, empy 4.x and possibly setuptools/pip are updated/need updating.