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
Additionally, the tarball SHA256 in the first pull request will now be invalid. At one time we had CI for osrf/homebrew-simulation to check for these kinds of errors, but that CI hasn't worked for a while (see osrf/homebrew-simulation#1139).
The text was updated successfully, but these errors were encountered:
Some approaches to solving this are to use a timestamp in the branch name so that the second invocation would open a duplicate pull request, or to identify the existing pull request and update the tarball SHA256 value
The following things occur as part of making a release with
release.py
:If a user runs the
release.py
script successfully one time and then runs it again without touching the osrfbuild/homebrew-simulation repository, steps 1-3 will succeed with a new tarball uploaded, but step 4 will fail as a branch with the desired name will already exist on the osrfbuild/homebrew-simulation repository (see https://build.osrfoundation.org/job/generic-release-homebrew_pull_request_updater/1413/).Additionally, the tarball SHA256 in the first pull request will now be invalid. At one time we had CI for osrf/homebrew-simulation to check for these kinds of errors, but that CI hasn't worked for a while (see osrf/homebrew-simulation#1139).
The text was updated successfully, but these errors were encountered: