-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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 13 pull requests #104428
Rollup of 13 pull requests #104428
Conversation
This was originally a part of rust-lang#100316. However, extracting it to a seperate PR should help with any extra testing that might be needed. Signed-off-by: Ayush Singh <[email protected]>
According to https://rust-lang.zulipchat.com/#narrow/stream/266220-rustdoc/topic/CSS.20cleanup this style was added for declarations that no longer use opacity.
please, please, don't match on `Symbol::as_str`s, every time you do, somewhere in the world another waffle becomes sad...
Spotted by @RalfJung. This causes no behavioural changes.
Because it's always false.
Because it's always empty.
…ipt, r=tmandry Adding Fuchsia compiler testing script, docs Adding Fuchsia compiler testing script and related docs updates r? `@tmandry` cc. `@djkoloski`
Remove leading newlines from `NonZero*` doc examples Like rust-lang#103045, but for `NonZero*`. `@rustbot` label A-docs
…nTitor Update compiler-builtins This was originally a part of rust-lang#100316. However, extracting it to a seperate PR should help with any extra testing that might be needed. Signed-off-by: Ayush Singh <[email protected]>
…r=GuillaumeGomez rustdoc: remove unused CSS `code { opacity: 1 }` According to https://rust-lang.zulipchat.com/#narrow/stream/266220-rustdoc/topic/CSS.20cleanup this style was added for declarations that no longer use opacity.
Remove dead NoneError diagnostic handling `NoneError` was removed some time ago, so this was dead code.
…em, r=compiler-errors Remove unused symbols and diagnostic items As the title suggests, this removes unused symbols from `sym::` and `#[rustc_diagnostic_item]` annotations that weren't mentioned anywhere. Originally I tried to use grep, to find symbols and item names that are never mentioned via `sym::name`, however this produced a lot of false positives (?), for example clippy matching on `Symbol::as_str` or macros "implicitly" adding `sym::`. I ended up fixing all these false positives (?) by hand, but tbh I'm not sure if it was worth it...
…ackh726 Deriving cleanups Fixing some minor problems `@RalfJung` found in rust-lang#99046. r? `@RalfJung`
Specify language of code comment to generate document Fix `let_underscore_drop` comment https://doc.rust-lang.org/rustc/lints/listing/allowed-by-default.html#example-7
…ation, r=notriddle Fix missing minification for static files It's a fix for rust-lang#101702. The problem was that `Path::ends_with` doesn't do what we thought it does: it checks if the entire item is the last path part, no just if the "path string" ends with the given argument. So instead, I just used the `extension()` method to get the information we want. cc `@jsha` r? `@notriddle` PS: Is it worth it to add a CI test to ensure that the minification was performed on JS and CSS files or not?
[llvm-wrapper] adapt for LLVM API change for llvm/llvm-project@feda983.
@bors r+ rollup=never p=10 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: previous master: 101e1822c3 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (ca92d90): comparison URL. Overall result: ❌ regressions - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
|
All the regressions are in @rust-timer build d5d26c0b90e16abe95721abdd3af630a23efd02b |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (d5d26c0b90e16abe95721abdd3af630a23efd02b): comparison URL. Overall result: ❌ regressions - ACTION NEEDEDBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
|
Yep, #104404 is definitely the cause of the regression. |
Justification for this regression was posted #104404. Effectively this regression is taking us back to the baseline. @rustbot label: +perf-regression-triaged |
Successful merges:
NonZero*
doc examples #104354 (Remove leading newlines fromNonZero*
doc examples)code { opacity: 1 }
#104380 (rustdoc: remove unused CSScode { opacity: 1 }
)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup