-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Run cargo update
in the project root
#129624
Conversation
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. These commits modify the If this was unintentional then you should revert the changes before this PR is merged. The list of allowed third-party dependencies may have been modified! You must ensure that any new dependencies have compatible licenses before merging. |
Adjust `memchr` pinning and run `cargo update` try-job: x86_64-pc-windows-gnu
This comment has been minimized.
This comment has been minimized.
@bors try |
Adjust `memchr` pinning and run `cargo update` try-job: x86_64-mingw
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
Hm. I assume this comes from |
@nagisa it looks like you maintain https://github.com/rust-lang/stacker, any clue if this is related? |
Sounds plausible enough. There's already a PR that bumps it on stacker side, so you'll be able to check this soon enough. |
Ignore the root Cargo.lock for now becuase stacker's Windows dependency may be problematic [1]. Link: rust-lang#129624 (comment) [1]
Okay, I dropped doing a @bors try |
Adjust `memchr` pinning and run `cargo update` try-job: x86_64-mingw
☀️ Try build successful - checks-actions |
☔ The latest upstream changes (presumably #130807) made this pull request unmergeable. Please resolve the merge conflicts. |
7f51490
to
1760d39
Compare
memchr
pinning and run cargo update
cargo update
in the project root
I dropped the library and rustbook changes from this PR, so updates are now spread across a couple smaller PRs:
Hoping that the MSVC failures isolate themselves to only a subset of these PRs. @bors r=Mark-Simulacrum |
☀️ Test successful - checks-actions |
miraculous |
I guess we have some pretty likely indicators that the library |
I'll try to see if anything in cc looks like it might cause problems. It's maybe a long shot though. |
Finished benchmarking commit (2bd1e89): 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)Results (secondary 2.9%)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.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 772.536s -> 774.091s (0.20%) |
@ChrisDenton, please look at this commit. It seems it is suspicious. |
That makes no practical difference. All DLLs are unloaded on process exit. |
try-job: x86_64-msvc
Part of #129538