-
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
Update sysinfo version to 0.31.2 #128436
Update sysinfo version to 0.31.2 #128436
Conversation
rustbot has assigned @Mark-Simulacrum. Use |
Seems like it's fine? r? @clubby789 |
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. Some changes occurred in src/tools/opt-dist cc @Kobzol |
You should try x86_64-pc-windows-gnu or x86_64-pc-windows-msvc? |
I have set @bors try |
Update sysinfo version to 0.31.0 I needed to update `memchr` version (which was pinned in rust-lang@36a1679). So let's see if it triggers the linker issue. try-job: x86_64-msvc
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
Looks like the |
I'm wondering the same thing. Checking what changed... |
c972a0e
to
fa2711b
Compare
Let's try again. @bors try |
Update sysinfo version to 0.31.0 I needed to update `memchr` version (which was pinned in rust-lang@36a1679). So let's see if it triggers the linker issue. try-job: x86_64-msvc
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
fa2711b
to
101235d
Compare
@bors try |
Update sysinfo version to 0.31.0 I needed to update `memchr` version (which was pinned in rust-lang@36a1679). So let's see if it triggers the linker issue. try-job: x86_64-msvc
💔 Test failed - checks-actions |
So still broken. Unfortunately, without updating
Which is quite surprising since I thought |
You're author of sysinfo, is it required to use latest versions of memchr? |
Discussion of the issue is on Zulip here |
I suppose it's not. |
You could try using |
Gonna give it a try. |
I think just writing |
101235d
to
d4c1082
Compare
d4c1082
to
f449586
Compare
Actually I also needed to remove the Let's try again. @bors try |
Update sysinfo version to 0.31.2 I needed to update `memchr` version (which was pinned in rust-lang@36a1679). So let's see if it triggers the linker issue. try-job: x86_64-mingw
☀️ Try build successful - checks-actions |
Seems like it's all good now! |
@bors r+ |
…lubby789 Update sysinfo version to 0.31.2 I needed to update `memchr` version (which was pinned in rust-lang@36a1679). So let's see if it triggers the linker issue. try-job: x86_64-mingw
Rollup of 5 pull requests Successful merges: - rust-lang#123994 (Use Default visibility for rustc-generated C symbol declarations) - rust-lang#126818 (Better handle suggestions for the already present code and fix some suggestions) - rust-lang#127624 (Migrate and rename `issue-47551`, `issue-35164` and `issue-69368` `run-make` tests to rmake) - rust-lang#128361 (Migrate `link-cfg` and `rustdoc-default-output` `run-make` tests to rmake) - rust-lang#128436 (Update sysinfo version to 0.31.2) r? `@ghost` `@rustbot` modify labels: rollup
…iaskrgr Rollup of 6 pull requests Successful merges: - rust-lang#126818 (Better handle suggestions for the already present code and fix some suggestions) - rust-lang#128436 (Update sysinfo version to 0.31.2) - rust-lang#128453 (raw_eq: using it on bytes with provenance is not UB (outside const-eval)) - rust-lang#128491 ([`macro_metavar_expr_concat`] Dogfooding) - rust-lang#128494 (MIR required_consts, mentioned_items: ensure we do not forget to fill these lists) - rust-lang#128521 (rustdoc: Remove dead opaque_tys rendering logic) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#128436 - GuillaumeGomez:update-sysinfo, r=clubby789 Update sysinfo version to 0.31.2 I needed to update `memchr` version (which was pinned in rust-lang@36a1679). So let's see if it triggers the linker issue. try-job: x86_64-mingw
I needed to update
memchr
version (which was pinned in 36a1679). So let's see if it triggers the linker issue.try-job: x86_64-mingw