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
{{ message }}
This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
It looks like there's a race condition between updating the companion's lock file and merging substrate PR to master.
Example: paritytech/polkadot#6035
The bot commited 2cadb32 with substrate updated to 37664fe5b3513eb996225f016eceaf74963b8133, which is not what the substrate companion merged to master (it's its parent).
I'd suggest figuring out the exact commit hash of the substrate PR to master and then using cargo update -p sp-io --precise <commit_sha>. This will also help when two PRs are merged without companions.
ordian
changed the title
use --precise in cargo update -p sp-io
check_dependent_project: use --precise in cargo update -p sp-ioOct 3, 2022
mordamax
transferred this issue from paritytech/pipeline-scripts
Oct 3, 2022
mordamax
changed the title
check_dependent_project: use --precise in cargo update -p sp-io
bot merge: companion was updated to old dependency commit
Oct 3, 2022
It looks like there's a race condition between updating the companion's lock file and merging substrate PR to master.
Example: paritytech/polkadot#6035
The bot commited 2cadb32 with substrate updated to 37664fe5b3513eb996225f016eceaf74963b8133, which is not what the substrate companion merged to master (it's its parent).
I'd suggest figuring out the exact commit hash of the substrate PR to master and then using
cargo update -p sp-io --precise <commit_sha>
. This will also help when two PRs are merged without companions.UPD:
The text was updated successfully, but these errors were encountered: