Skip to content

refactor: address unsafe-op-in-unsafe-fn for Windows #15876

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

weihanglo
Copy link
Member

What does this PR try to resolve?

See #15790 (comment) and
https://triage.rust-lang.org/gha-logs/rust-lang/rust/48570988075#2025-08-21T12:21:45.8237728Z

We don't run clippy on Windows so we never catch that.

We don't run clippy on Windows so we never catch that.
@rustbot
Copy link
Collaborator

rustbot commented Aug 21, 2025

r? @epage

rustbot has assigned @epage.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Aug 21, 2025
@weihanglo
Copy link
Member Author

error: test failed, to rerun pass -p cargo --test testsuite
Caused by:
process didn't exit successfully: C:\a\cargo\cargo\target\debug\deps\testsuite-5bacec5b68ca9ba2.exe (exit code: 0xc0000005, STATUS_ACCESS_VIOLATION)
note: test exited abnormally; to see the full output pass --nocapture to the harness.
C:\a_temp\f2c1a125-7845-41f4-9396-be72dd354d2a.sh: line 1: 1375 Segmentation fault cargo test -p cargo
Error: Process completed with exit code 139.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants