-
Notifications
You must be signed in to change notification settings - Fork 97
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
Sync gpgme error: Unusable secret key #902
Comments
There was just another instance of this today: https://build.ros2.org/job/Grel_sync-packages-to-testing_focal_arm64/104/consoleFull
|
There was another instance of this on Melodic as well: https://build.ros.org/job/Mrel_sync-packages-to-testing_bionic_amd64/726/console
|
These last jobs failed within a minute of each other on separate days. Do we have a server maintenance task managing the gpg keys at that time? The earlier case is also just before the hour too. |
I saw a similar but different GPG error importing the jammy repositories today. https://build.ros2.org/job/import_upstream/357/ I am going to block out some time for this toward the start of next year. |
This error suddenly came up in one of my packages today: https://build.ros2.org/job/Hrel_import-package/4137/consoleFull This is the job that triggered the Hrel_import_package: https://build.ros2.org/job/Hbin_ujv8_uJv8__rqt_image_overlay_layer__ubuntu_jammy_arm64__binary/4/consoleFull Update The build passed in the next build "Started by user SYSTEM": https://build.ros2.org/job/Hbin_ujv8_uJv8__rqt_image_overlay_layer__ubuntu_jammy_arm64__binary/5/ without any changes. |
Just caught another instance of this: https://build.ros2.org/job/Rbin_ujv8_uJv8__rcss3d_agent_msgs__ubuntu_jammy_arm64__binary/32/ |
We had another instance of this for noetic sync to testing: https://build.ros.org/view/Nbin_uF64/job/Nrel_sync-packages-to-testing_focal_amd64/1134/console It's likely still happening in the background for individual package syncs but they retry sooner so as not to be noticed. |
I'm refiling osrf/infrastructure#3 (comment) here so that we can track this.
The text was updated successfully, but these errors were encountered: