Update the rustc_perf submodule#158245
Conversation
|
|
|
This comment has been minimized.
This comment has been minimized.
|
The list of allowed third-party dependencies may have been modified! You must ensure that any new dependencies have compatible licenses before merging. |
|
Note that 'new benchmarks' here largely doesn't matter, we filter down what is actually executed in CI here: rust/src/build_helper/src/lib.rs Lines 14 to 36 in cddcbec But I think it's good to keep the submodule somewhat up to date regardless, to reduce drift / unrelated issues creeping in when we do need to tweak it. |
|
well, it matters for local perf runs ( |
4db46f7 to
f79fa40
Compare
|
See #t-compiler/contrib-private > Licenses for the discussion on license changes, the upshot it: it's probably fine to do what this PR does |
|
@bors try @rust-timer queue (Not expecting any issues but let's make sure). |
This comment has been minimized.
This comment has been minimized.
|
r? me |
This comment has been minimized.
This comment has been minimized.
Update the rustc_perf submodule
|
💔 Test for 63cc3b0 failed: CI. Failed job:
|
This comment has been minimized.
This comment has been minimized.
|
CI is incredibly flaky today and the past few days. |
f79fa40 to
7a742bc
Compare
This comment has been minimized.
This comment has been minimized.
Update the rustc_perf submodule
|
💔 Test for f1604c6 failed: CI. Failed job:
|
This comment has been minimized.
This comment has been minimized.
7a742bc to
2bd04b2
Compare
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
2bd04b2 to
a6bd564
Compare
|
@rustbot review |
|
@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.
Update the rustc_perf submodule
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (38c9cd6): comparison URL. Overall result: ❌ regressions - no action neededBenchmarking means the PR may be perf-sensitive. Consider adding rollup=never if this change is not fit for rolling up. @rustbot label: -S-waiting-on-perf -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 1.8%, secondary -4.7%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesThis perf run didn't have relevant results for this metric. Binary sizeResults (primary -0.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 491.018s -> 490.18s (-0.17%) |
|
Looks good, thank you! @bors r+ rollup |
…Kobzol Update the rustc_perf submodule I hope this is a thing that's ok to do, I never update submodules but this one seems to be 8 months old and we got some new benchmarks in the meantime. r? @Kobzol
Rollup of 13 pull requests Successful merges: - #158478 (Use correct typing mode in mir building for the next solver) - #158796 (Distinguish null reference production from null pointer dereference in UB checks) - #158821 (add regression test for late-bound type method probe ICE) - #158245 (Update the rustc_perf submodule) - #158346 (Prevent rustdoc auto-trait ICEs with `-Znext-solver=globally`) - #158536 (Instatiate binder instead of skipping when suggesting function arg error) - #158553 (Avoid infinite recursion when trying to build valtrees for self-referential consts) - #158679 (Document blocking guarantees for `std::sync`) - #158826 (Reorganize `tests/ui/issues` [19/N]) - #158860 (Delete `impl_def_id` field from `ImplHeader`) - #158867 (rewrite `Align::max_for_target` in a more obvious way) - #158878 (borrowck: Inline `free_region_constraint_info()` to simplify the code) - #158881 (Update mdbook to 0.5.4)
View all comments
I hope this is a thing that's ok to do, I never update submodules but this one seems to be 8 months old and we got some new benchmarks in the meantime.
r? @Kobzol