-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Call module_name_to_str instead of just unwrapping #130680
Conversation
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.
Thanks!
@bors r+ rollup |
…youxu Call module_name_to_str instead of just unwrapping This makes the ICE message in rust-lang#130678 more clear. It looks like not calling this function was just an oversight in rust-lang#76859, but clearly not a major one because it's taken us 4 years to notice.
…llaumeGomez Rollup of 5 pull requests Successful merges: - rust-lang#129545 (rustdoc: redesign toolbar and disclosure widgets) - rust-lang#130658 (Fix docs of compare_bytes) - rust-lang#130670 (delay uncapping the max_read_size in File::read_to_end) - rust-lang#130680 (Call module_name_to_str instead of just unwrapping) - rust-lang#130690 (interpret: remove outdated FIXME) r? `@ghost` `@rustbot` modify labels: rollup
I wonder if this is the one which failed in #130695. |
That's an exotic failure mode. Let's see! @bors try |
🙅 Please do not |
@bors r- |
@bors try |
Call module_name_to_str instead of just unwrapping This makes the ICE message in rust-lang#130678 more clear. It looks like not calling this function was just an oversight in rust-lang#76859, but clearly not a major one because it's taken us 4 years to notice. try-job: i686-msvc
☀️ Try build successful - checks-actions |
Well. Having looked through the other PRs in that rollup I agree with @GuillaumeGomez that nothing else in there looks related. But also I cannot explain how this PR would corrupt a DenseMap, and we just passed a try build for the job that failed, so either this PR is fine or the failure is nondeterministic. @bors r=jieyouxu rollup=never just in case this needs to be reverted or fails again |
☀️ Test successful - checks-actions |
Finished benchmarking commit (d14c1c7): comparison URL. Overall result: ❌ regressions - 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)Results (primary 0.3%, secondary -0.8%)This 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.
CyclesResults (primary 0.5%, secondary 3.1%)This 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.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 769.792s -> 770.325s (0.07%) |
This makes the ICE message in #130678 more clear. It looks like not calling this function was just an oversight in #76859, but clearly not a major one because it's taken us 4 years to notice.
try-job: i686-msvc