-
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 6 pull requests #110127
Rollup of 6 pull requests #110127
Conversation
Part 3: Finishing `collect.rs` file
Fix formatting that rustfmt can't handle currently. Co-authored-by: Michael Goulet <michael@errs.io>
…rs-method-probe, r=jackh726 Instantiate instead of erasing binder when probing param methods Fixes rust-lang#108836 There is a really old comment saying that a `WhereClauseCandidate` probe candidate "should not contain any inference variables", but I'm not really confident that that comment applies anymore. In contrast, other candidates that we assemble during method probe contain inference variables in their substitutions (e.g. `InherentImplCandidate`)... Since this change is made only to support a nightly feature, I'm happy to gate the new behavior behind this feature flag or discuss it further. r? types
…errors Add little `is_test_crate` function Ok, this is quite a story. I'm mainly a Clippy contributor, so I was fixing [this Clippy issue](rust-lang/rust-clippy#10584) about a lint having to ignore test modules but that wasn't ignoring test files (integration test, `test/` dirs and such). As test **files** don't tend to have an inner `#[cfg(test)]` module inside them, I tried everything, looking for filenames, looking for item's parents in the HIR Map, doing black magic... I even asked [on Zulip](https://rust-lang.zulipchat.com/#narrow/stream/122651-general/topic/.E2.9C.94.20Checking.20if.20file.20is.20integration.20test), and jyn answered something about `--cfg test`. Aha! That's something that I might be looking for, so I started looking at `rustc_driver_impl` flag parsing and configuration and all that. Then, I stumbled on [this function right here](https://github.com/rust-lang/rust/blob/2e486be8d29d198d48bc26bfce5712a4822814f5/compiler/rustc_driver_impl/src/lib.rs#L174-L181), and noticed the argument `config: Config`. That's a hint. So [Config](https://doc.rust-lang.org/beta/nightly-rustc/rustc_interface/interface/struct.Config.html) has the field `opts: Options`, and [`Options`](https://doc.rust-lang.org/beta/nightly-rustc/rustc_session/options/struct.Options.html) has the field `test`. This journey has been ~7 or 8 hours in 3 days, it's a very hard thing to find, so this PR adds a mini-function to check if the current crate is a testing one. So that no one has to travel through the same as me, and can just search for `is_test_crate` in the documentation.
…tics-3, r=compiler-errors Migrate `rustc_hir_analysis` to session diagnostic [Part 3] Part 3: Finishing `collect.rs` file r? ``@compiler-errors``
…, r=compiler-errors Migrate remainder of rustc_ty_utils to `SessionDiagnostic` This moves the remaining errors in `rust_ty_utils` to `SessionsDiagnostic`. r? ``@davidtwco``
…gelog, r=ozkanonur Add renaming of ignore-git to changelog `bootstrap`'s `ignore-git` option has been renamed to `omit-git-hash` in rust-lang#110059. This PR adds this change to the `CHANGELOG.md`. See also rust-lang#110020 (comment).
compiletest: Give a better error message if `node` isn't installed
@bors r+ rollup=never p=6 |
⌛ Testing commit dd5942d with merge b845362c5b6f3077313b1a52eaecd31c3fb9bdf1... |
💔 Test failed - checks-actions |
⌛ Testing commit dd5942d with merge f5c05d46a95a14916f3179b8847f79efce99bcee... |
💔 Test failed - checks-actions |
@bors retry crates.io network blip |
⌛ Testing commit dd5942d with merge b6d27939c490f5a9438c6b1815c7fcad9d18b438... |
💔 Test failed - checks-actions |
@bors treeclosed=10 crates.io is still failing |
@bors retry p=10 |
@bors treeclosed- Looks like it is resolved. |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: previous master: 696aaad58c In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (3c2e2dd): comparison URL. Overall result: ✅ improvements - no action needed@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.
|
Successful merges:
is_test_crate
function #109985 (Add littleis_test_crate
function)rustc_hir_analysis
to session diagnostic [Part 3] #110028 (Migraterustc_hir_analysis
to session diagnostic [Part 3])SessionDiagnostic
#110095 (Migrate remainder of rustc_ty_utils toSessionDiagnostic
)node
isn't installed #110114 (compiletest: Give a better error message ifnode
isn't installed)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup