Fix: workaround when apt GPG key is mismatch #10
Conversation
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
- If apt-get update fails, update the GPG key. - Disabling workflow_dispatch event.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
apt-get updatefails, update the GPG key.workflow_dispatchevent (because it is a public repo).The actual testing step fails continuously but the
apt-get updatestep passed. ("Install additional packages")https://github.com/Futu-reADS/autoware_bridge/actions/runs/15437554964/job/43447363359
The result of the commands in the case that the apt key of ROS is unmatched, see following. It was done with commenting out the first
apt-get update. (there would be no way to reproduce)https://github.com/Futu-reADS/autoware_bridge/actions/runs/15434901934/job/43439287556
Both of the logs fail at
RoutePlanningTest.TestRoutePlanningFailurein the "Test" step of the workflow.It seems to finish in 7ms when it is occasionally successful, but it appears to stall here in these logs.