You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We noticed in osrf/homebrew-simulation#2265 (comment) that the generic-release-homebrew_pr_bottle_hash_updater job (which is one of 2 jobs triggered after a successful bottle build) is sometimes flaky:
Currently only the https://build.osrfoundation.org/job/generic-release-homebrew_triggered_bottle_builder/ is recorded in the build status, so we don't see if the bottle hash updater job fails. It would be helpful if both jobs triggered after a successful bottle build (the uploader and the hash updater) were included in the build status so we could confirm that they passed before merging.
The text was updated successfully, but these errors were encountered:
We noticed in osrf/homebrew-simulation#2265 (comment) that the generic-release-homebrew_pr_bottle_hash_updater job (which is one of 2 jobs triggered after a successful bottle build) is sometimes flaky:
Currently only the https://build.osrfoundation.org/job/generic-release-homebrew_triggered_bottle_builder/ is recorded in the build status, so we don't see if the bottle hash updater job fails. It would be helpful if both jobs triggered after a successful bottle build (the uploader and the hash updater) were included in the build status so we could confirm that they passed before merging.
The text was updated successfully, but these errors were encountered: