Bump action-ros-ci to v0.2#165
Closed
matthew-reynolds wants to merge 1 commit intoros-controls:masterfrom
Closed
Conversation
Member
Author
|
And of course, CI fails here without #164 due to flakey JTC tests 🤦♂️ We should be able to just rerun the CI on this PR to get it to pass though. I don't have permissions to rerun the job, can a maintainer rerun it? |
Merged
destogl
approved these changes
Apr 7, 2021
This was referenced Apr 24, 2021
Closed
Member
|
I'll close this for now, @matthew-reynolds feel free to reopen when a good reason to move presents itself. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Bump
ros-tooling/action-ros-cito v0.2Summary
Looks like the recent release of
ros-tooling/setup-rosv0.1.3 pulled in a newer version ofcolcon-mixin, which elevated a warning to an error: ros-tooling/action-ros-ci#525 (comment)This causes
ros-tooling/action-ros-cito fail out. The easiest approach is to just switch to the recently-released v0.2 and update our mixin rules according to ros-tooling/action-ros-ci#591Testing To Do