-
-
Notifications
You must be signed in to change notification settings - Fork 12
Remove check for .yaml modification before recipe generated in testpr CI job and fix testpr job #40
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
Conversation
@traversaro - do you want to remove all checks for any changes in yml/yaml files? Check my latest commit for hints |
Thanks I had totally missed that. Yes, perhaps just running the CI on all PRs seems easier? All those checks come from pre-snapshot times, but now with snapshot if no new packages build are triggered, the CI check should be a really fast check (modulo bugs), so I think it would be great to just remove the checks and always run CI? |
To clarify, my proposal is fee2a0e . I also added a |
Windows is failing with:
I vaguely remember seeing this as a warning before, so I guess it could make sense to just pin cmake to 3.* for now. |
So I think we need to read in the snapshot file, otherwise we'll rebuild newer versions of packages that have been built since the last rebuild, and that might lead to ABI incompatibilities. |
I am probably missing something, but aren't we already reading the snapshot file? |
I don’t think we do - it’s neither in the testpr.yml nor main.yml |
Ah, yes - thanks , jet lagged me! |
As we introduced several modifications in 2025, such as the use of rosdistro snapshot instead of always building the latest rosdistro, and the use of
pkg_additional_info.yaml
to bump the build number of packages that we want to rebuild, the check forvinca_*.yaml
modification before running PR does not make a lot of sense. If a PR is not triggering the build of new packages, then the build step is super fast, and if instead a new recipe is triggered without us being aware of this, it is important that the PR CI catches the unintentional package generation.xref: RoboStack/ros-humble#277