-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Remove resolver=2 from Cargo.toml and add it to the Windows build #26706
Remove resolver=2 from Cargo.toml and add it to the Windows build #26706
Conversation
…t resolver=2 for Windows builds.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
echo ${{ secrets.GITHUB_TOKEN }} | gh auth login --with-token | ||
git config --global user.email "<>" | ||
git config --global user.name "Github Action Bot" | ||
git add -u | ||
git commit -m "Add resolver=2" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe we don't want to commit here. ci/publish-tarball.sh creates a version.yml depends on the latest commit. if we do a new commit, I think it makes windows's version.yml will always different from linux and mac.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah good catch. I moved the logic into ci/publish-tarball.sh so it's after the git reset --hard
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@willhickey @yihau how about backporting this to v1.10 branch? do you see any concerns? this pr has been in for awhile in master and causing no problem? as a context, I'm intending to ship #26555 to v1.10. |
just installed an edge bin on windows. I think it works fine. |
@willhickey @yihau oops. it looks like this pr isn't needed for #26555 actually. sorry. I'm reverting this. I was seeing odd error because, i.e. this works: # This prevents a Travis CI error when building for Windows.
resolver = "2"
+
+# for details, see https://github.com/solana-labs/crossbeam/commit/fd279d707025f0e60951e429bf778b4813d1b6bf
+[patch.crates-io]
+crossbeam-epoch = { git = "https://github.com/solana-labs/crossbeam", rev = "fd279d707025f0e60951e429bf778b4813d1b6bf" this won't: +
+# for details, see https://github.com/solana-labs/crossbeam/commit/fd279d707025f0e60951e429bf778b4813d1b6bf
+[patch.crates-io]
+crossbeam-epoch = { git = "https://github.com/solana-labs/crossbeam", rev = "fd279d707025f0e60951e429bf778b4813d1b6bf"
# This prevents a Travis CI error when building for Windows. <= Even this comment doesn't terminate the preceeding patch section parsing context...
resolver = "2" # <= this is now meaning to patch a non-existing crate called `resolver`... I'm dumb
|
…uild" (backport #27011) (#27019) Revert "Remove resolver=2 from Cargo.toml and add it to the Windows build" (#27011) Revert "Remove resolver=2 from Cargo.toml and add it to the Windows build (#26706)" This reverts commit 2f6f5b1. (cherry picked from commit ecda3be) Co-authored-by: Ryo Onodera <ryoqun@gmail.com>
…uild" (backport #27011) (#27024) Revert "Remove resolver=2 from Cargo.toml and add it to the Windows build" (#27011) Revert "Remove resolver=2 from Cargo.toml and add it to the Windows build (#26706)" This reverts commit 2f6f5b1. (cherry picked from commit ecda3be) Co-authored-by: Ryo Onodera <ryoqun@gmail.com>
…uild" (solana-labs#27011) Revert "Remove resolver=2 from Cargo.toml and add it to the Windows build (solana-labs#26706)" This reverts commit 2f6f5b1.
See discussion on PR #26555
Problem
PR #24196 added
resolver = "2"
to Cargo.toml. That fixed the broken Windows build but is causing other problems (see #22603)Summary of Changes
resolver = "2"
from Cargo.tomlresolver = "2"
to the local copy of Cargo.toml immediately before the build.context #22603