Make rustc_hir_analysis not depend on rustc_lint.#154338
Make rustc_hir_analysis not depend on rustc_lint.#154338nnethercote wants to merge 1 commit intorust-lang:mainfrom
rustc_hir_analysis not depend on rustc_lint.#154338Conversation
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
…<try> Make `rustc_hir_analysis` not depend on `rustc_lint`.
This comment has been minimized.
This comment has been minimized.
|
@bors try cancel |
|
Try build cancelled. Cancelled workflows: |
aa5614f to
56d9046
Compare
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
…<try> Make `rustc_hir_analysis` not depend on `rustc_lint`.
|
The job Click to see the possible cause of the failure (guessed by this bot) |
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (e9a5683): comparison URL. Overall result: no relevant changes - no action neededBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. @bors rollup=never Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results (secondary -2.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -2.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 485.223s -> 490.41s (1.07%) |
|
Eliminating an inter-crate dependency that was on the critical path in my local build somehow made CI bootstrap builds 5s slower. Sigh. |
|
@nnethercote This could also be noise. Most of the regression is 5s on one crate. We seem to get more and more of these single crate spikes recently: https://perf.rust-lang.org/bootstrap.html?start=2025-11-01 |
|
Would running it again be worthwhile? |
|
Maybe? AFAIK it's not clear what causes those spikes - i.e. whether it comes from the built artifact or the benchmarking machine. If we try with a different base commit, I'd think it's unlikely to hit the same spike again, no matter what the source is. But they seem to get more frequent, so maybe not. |
|
Ok, I'll try again in #154361. |
No description provided.