-
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
Override rustc version in ui and mir-opt tests to get stable hashes #92363
Override rustc version in ui and mir-opt tests to get stable hashes #92363
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
664a79e
to
e0611f7
Compare
This comment has been minimized.
This comment has been minimized.
e0611f7
to
d057342
Compare
This comment has been minimized.
This comment has been minimized.
d057342
to
9d4ee23
Compare
This comment has been minimized.
This comment has been minimized.
9d4ee23
to
e49b06d
Compare
This comment has been minimized.
This comment has been minimized.
e49b06d
to
038a82d
Compare
038a82d
to
2a818de
Compare
This comment has been minimized.
This comment has been minimized.
2a818de
to
4694f87
Compare
It looks like this is mixing the incr-comp hash noise removal with a bunch of unrelated(?) changes to move regex's to lazy_static! -- is that right? Can we at least mention that in the PR description + commit message, or ideally split that bit out into a separate commit? (Happy to review it as part of this PR, if you want). |
My goal was to improve performance. The bottleneck was regex creation. This required But sure, I can extract a) into another commit. |
Yeah, that makes sense (and is a great goal, thanks!) -- just want to make sure I'm reviewing with the right things in mind. Splitting out (b) from (c), presuming it is sort of independent which it sounds like it would be for at least some of the normalizing variables may also make sense. |
That'd be more work to tease them apart since I just relied on bless and the test results to see which files need to get updated and didn't pay attention to which change affected what. I'd like to avoid that if it's ok. |
Sounds good, no worries. |
4694f87
to
e4e3b64
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r=me with a comment added
@bors r- |
☔ The latest upstream changes (presumably #87648) made this pull request unmergeable. Please resolve the merge conflicts. |
f081c21
to
852085d
Compare
rebased, updated the variable and re-blessed the test outputs. @bors r=Mark-Simulacrum |
📌 Commit 852085dd257afb14b823113101733cab26c58fc9 has been approved by |
Building a dozen separate regexps for each test in compiletest consumes significant amounts of CPU cycles. Using `RUSTC_FORCE_INCR_COMP_ARTIFACT_HEADER` stabilizes hashes calcuated for the individual tests so no test-dependent normalization is needed. Hashes for the standard library still change so some normalizations are still needed.
852085d
to
7a5796d
Compare
rebased and reblessed @bors r=Mark-Simulacrum |
📌 Commit 7a5796d has been approved by |
@bors rollup=never |
☀️ Test successful - checks-actions |
Finished benchmarking commit (17d29dc): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
Building a dozen separate regexps for each test in compiletest consumes significant amounts of CPU cycles.
UI test timings on my machine:
OLD: 39.63s
NEW: 30.27s