-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Bump cc
for bootstrap
#111701
Bump cc
for bootstrap
#111701
Conversation
Bump the version of dependency `cc` to v1.0.77 for `bootstrap`, syncing with rust/Cargo.lock Resolves rust-lang#111700
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ozkanonur (or someone else) soon. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
@bors r+ rollup Thanks! |
Bump `cc` for `bootstrap` Bump the version of dependency `cc` to `1.0.77` for `bootstrap`, syncing with `rust/Cargo.lock` Resolves rust-lang#111700
Bump `cc` for `bootstrap` Bump the version of dependency `cc` to `1.0.77` for `bootstrap`, syncing with `rust/Cargo.lock` Resolves rust-lang#111700
Bump `cc` for `bootstrap` Bump the version of dependency `cc` to `1.0.77` for `bootstrap`, syncing with `rust/Cargo.lock` Resolves rust-lang#111700
Bump `cc` for `bootstrap` Bump the version of dependency `cc` to `1.0.77` for `bootstrap`, syncing with `rust/Cargo.lock` Resolves rust-lang#111700
@bors rollup=iffy |
⌛ Testing commit d371b80 with merge e1013a37f5a22aca970190dcbdfb96a4b6b7e871... |
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
cc @thomcc, seems like something regressed between cc 1.0.73 and .77. any idea what might have changed? |
This version also resolves rust-lang#111700, try if we can bump to this release without regression.
@r-value fyi i don't want to bisect this in a full bors merge because it'll get merged if the test succeeds - feel free to test with PR CI though: https://rustc-dev-guide.rust-lang.org/tests/ci.html#using-ci-to-test |
Thank you very much for your suggestion! Actually, I'm pushing the commit because I think that if 1.0.74 works then it might have a chance to meet the merge window on May 26th so that we can resolve the issue ~1mo earlier. It's not a bisect because I'm not gonna push more commit if this fails :). |
I don't want to merge 1.0.74. Let's figure out why this regressed and fix it either upstream or here.
I don't mind beta-nominating the PR for a backport once we figure out the right fix. |
Thanks! Then what should I do about this branch? a force-push or leave it alone? |
Once you figure out the problem, force-pushing the fix so it's one commit would be good. Anything you want to do with it in the meantime is fine since it won't get merged. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I'm not familiar with Apple dev/test environments, but I suspect that rust-lang/cc-rs#661 may have set a wrong Here is a diff between config commands of a succeeded and a failed test run. --- fail.txt 2023-05-23 09:20:37.218611111 +0200
+++ success.txt 2023-05-23 09:20:05.004982583 +0200
@@ -32,7 +32,7 @@ DESTDIR=""
-m64
-mios-simulator-version-min=7.0
-isysroot
-/Applications/Xcode_13.4.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk
+/Applications/Xcode_13.4.1.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator15.5.sdk
-fembed-bitcode
-fdebug-prefix-map=/Users/runner/work/rust/rust=/rustc/llvm
-miphoneos-version-min=10.0
@@ -42,7 +42,7 @@ DESTDIR=""
-m64
-mios-simulator-version-min=7.0
-isysroot
-/Applications/Xcode_13.4.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk
+/Applications/Xcode_13.4.1.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator15.5.sdk
-fembed-bitcode
-fdebug-prefix-map=/Users/runner/work/rust/rust=/rustc/llvm
-fembed-bitcode=off"
@@ -59,6 +59,6 @@ DESTDIR=""
-m64
-mios-simulator-version-min=7.0
-isysroot
-/Applications/Xcode_13.4.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk
+/Applications/Xcode_13.4.1.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator15.5.sdk
-fembed-bitcode"
"-DCMAKE_BUILD_TYPE=Release" |
This comment has been minimized.
This comment has been minimized.
Looks like you didn't tried latest version or master branch, maybe already fixed? |
TBH I don't think it is fixed because it's still accepting |
This comment has been minimized.
This comment has been minimized.
I found something interesting here: rust/src/ci/scripts/install-clang.sh Lines 30 to 35 in f3d597b
Maybe we need to set SDKROOT more precisely or just remove that since it will be ignored anyway if it has a mismatched value against current target.I'll try to remove these code for now. |
The job Click to see the possible cause of the failure (guessed by this bot)
|
PR was closed due to inactivity. If you plan to work on it again, you can reopen it. |
Bump the version of dependency
cc
to1.0.77
forbootstrap
, syncing withrust/Cargo.lock
Resolves #111700