-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Rollup of 6 pull requests #97159
Merged
Merged
Rollup of 6 pull requests #97159
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We currently upload approximately 166 GB/day into this bucket (estimate based on duration of storage and total current size). My estimate is that this change should decrease our costs (which are currently in credits) and is in the worst case (if all objects are brought into hot storage due to unanticipated frequent access) only going to add an additional ~$4 to the monthly bill. If access is rare (as expected) to most objects then we expect to save approximately ~$350/month (after this change takes full effect in ~168 days).
There is no reason it needs to be lazily computed at the first iteration of the cgu loop.
This reduces the complexity of this code a lot
…-ci, r=pietroalbini Switch CI bucket uploads to intelligent tiering We currently upload approximately 166 GB/day into this bucket (estimate based on duration of storage and total current size). My estimate is that this change should decrease our costs (which are currently in credits) and is in the worst case (if all objects are brought into hot storage due to unanticipated frequent access) only going to add an additional ~$4 to the monthly bill. If access is rare (as expected) to most objects then we expect to save approximately ~$350/month (after this change takes full effect in ~168 days). r? ``@pietroalbini``
…mpiler-errors Couple of refactorings to cg_ssa::base::codegen_crate This makes the code simpler and easier to read.
…u-se Revert "Auto merge of rust-lang#96441 - ChrisDenton:sync-pipes, r=m-ou-se" This reverts commit ddb7fbe. Partially addresses rust-lang#97124, but not marking as fixed as we're still pending on a beta backport (for 1.62, which is happening in rust-lang#97088). r? ``@m-ou-se`` ``@ChrisDenton``
Improve println! documentation
…neration, r=notriddle Move some settings DOM generation out of JS The first commit reduce the JS size a bit by moving some DOM content generation into the HTML file directly. The second commit is an update of the `browser-ui-test` version which improves `wait-for-*` command (if the element doesn't exist, it'll wait for it instead of failing). r? ``@notriddle``
Update cargo 3 commits in 3f052d8eed98c6a24f8b332fb2e6e6249d12d8c1..a4c1cd0eb6b18082a7e693f5a665548fe1534be4 2022-05-12 15:19:04 +0000 to 2022-05-18 01:52:07 +0000 - Add notes about pre-stabilization to contributor unstable docs (rust-lang/cargo#10675) - reference: Update syntax supported by `rustc-link-lib` (rust-lang/cargo#10674) - Correct the release dates for 1.61 and 1.62 (rust-lang/cargo#10665)
@bors r+ p=6 rollup=never |
📌 Commit 9babb1c has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (e6327bc): comparison url. Summary: This benchmark run did not return any relevant results. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
merged-by-bors
This PR was explicitly merged by bors.
rollup
A PR which is a rollup
S-waiting-on-bors
Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
T-libs
Relevant to the library team, which will review and decide on the PR/issue.
T-rustdoc
Relevant to the rustdoc team, which will review and decide on the PR/issue.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Successful merges:
Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup