-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Prepare 1.85 beta release #135163
Prepare 1.85 beta release #135163
Conversation
@bors r+ p=100 |
Prepare 1.85 beta release r? `@ghost`
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
Turns out that Manually removed the broken replacement from the commit, will send a tooling change later. @bors r+ p=100 |
@bors rollup=never |
This comment has been minimized.
This comment has been minimized.
@bors r- PR CI failed. Will investigate. |
Prepare 1.85 beta release r? `@ghost`
Congrats bors you're broken. @bors retry |
When `-Cstrip` was changed to use the bundled rust-objcopy instead of /usr/bin/strip on OSX, strip-like arguments were preserved. But strip and objcopy are, while being the same binary, different, they have different defaults depending on which binary they are. Notably, strip strips everything by default, and objcopy doesn't strip anything by default. Additionally, `-S` actually means `--strip-all`, so debuginfo stripped everything and symbols didn't strip anything. We now correctly pass `--strip-debug` and `--strip-all`.
Some changes occurred in src/doc/rustc/src/check-cfg.md cc @Urgau |
Whoops that commit was on my work laptop, not my personal laptop 😅 @bors retry r+ p=100 rollup=never |
Prepare 1.85 beta release r? `@ghost`
⌛ Testing commit 3d6fdff with merge fd27cb9eb83361bf3720a0010e22c5b8035ef129... |
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
Same error as the one encountered when preparing the previous beta version, #133447 (comment) |
☀️ Test successful - checks-actions |
…ark-Simulacrum Revert rust-lang#131365 This PR reverts rust-lang#131365, following the revert we did on the beta branches for both 1.84 and 1.85. While the PR passes CI successfully on master, as soon as we branch off beta it starts failing in the newly created beta branch. This caused the release team to revert it for both 1.84 and 1.85, and if nothing is done it would continue being reverted every cycle. `@heiseish` (PR author) feel free to submit the PR again in the future: this revert doesn't represent the release team rejecting your change, but just a (hopefully temporary!) revert to ensure future beta branches can be created without reverting it each time. When submitting the PR again, I recommend you test your changes by configuring `rust.channel` to both `nightly` and `beta` in your `config.toml`. You can see the latest failure [here](rust-lang#135163 (comment)).
r? @ghost