-
Notifications
You must be signed in to change notification settings - Fork 30
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
Add a global CI job for infrastructure packages #308
base: ros2
Are you sure you want to change the base?
Conversation
build_environment_variables: | ||
PYTHONWARNINGS: 'ignore:pkg_resources::' | ||
build_tool: colcon | ||
build_tool_test_args: '--event-handler console_stderr- console_cohesion+ --executor parallel --python-testing pytest --pytest-args -k "not test_spell_check" --packages-skip superflore' |
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.
Is superflore being skipped because tests aren't passing on HEAD?
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.
That's correct. I think at least some of them may need a functioning container engine.
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.
cc @robwoolley since you have been getting superflore tests up and running.
The intent for this job is to regularly build and test the bleeding edge of all of our infrastructure packages. Because these packages aren't part of any ROS distribution, the development tip is not regularly tested.
As we narrow in on a blessed development environment for our infrastructure packages as a whole (what linters/plugins are expected), we can add more packages to this job and tweak the build/test args to expand our coverage. This is a pretty good starting point, but there are notably absent packages like
ros_buildfarm
itself, which doesn't work due to setuptools compatibility.Requires: ros-infrastructure/ros_buildfarm#1056
Requires: ros-infrastructure/ros_buildfarm#1057Staging deployment: https://build.test.ros2.org/job/ci__infra_ubuntu_noble_amd64/