Skip to content

Miri subtree update #139630

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

Merged
merged 14 commits into from
Apr 10, 2025
Merged

Miri subtree update #139630

merged 14 commits into from
Apr 10, 2025

Conversation

RalfJung
Copy link
Member

r? @ghost

a sync is needed to fix the miri-test-libstd failures

CraftSpider and others added 13 commits April 6, 2025 11:13
- consistent handling, invalid handles are always an abort
- Helper for reading handles that does the checking and machine stop
- Use real handle types more places
- Adds `File` and `Invalid` types of handle. File support will be added next
Support getting file metadata on Windows
triagebot: enable `[canonicalize-issue-links]` and `[no-mentions]`
Implement FreeBSD syscall _umtx_op  for futex support
@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Apr 10, 2025
@rustbot
Copy link
Collaborator

rustbot commented Apr 10, 2025

The Miri subtree was changed

cc @rust-lang/miri

@rustbot
Copy link
Collaborator

rustbot commented Apr 10, 2025

These commits modify the Cargo.lock file. Unintentional changes to Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

@RalfJung
Copy link
Member Author

@bors r+ p=1

@bors
Copy link
Collaborator

bors commented Apr 10, 2025

📌 Commit 955d92f has been approved by RalfJung

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Apr 10, 2025
@RalfJung
Copy link
Member Author

Odd, PR CI never triggered for the most recent commit...

@RalfJung RalfJung closed this Apr 10, 2025
@RalfJung RalfJung reopened this Apr 10, 2025
@RalfJung
Copy link
Member Author

@bors r+ p=1

@bors
Copy link
Collaborator

bors commented Apr 10, 2025

💡 This pull request was already approved, no need to approve it again.

@bors
Copy link
Collaborator

bors commented Apr 10, 2025

📌 Commit 955d92f has been approved by RalfJung

It is now in the queue for this repository.

bors added a commit to rust-lang-ci/rust that referenced this pull request Apr 10, 2025
…iaskrgr

Rollup of 7 pull requests

Successful merges:

 - rust-lang#139502 (fix "still mutable" ice while metrics are enabled)
 - rust-lang#139510 (Rename some `name` variables as `ident`.)
 - rust-lang#139606 (Update compiletest to Edition 2024)
 - rust-lang#139609 (compiletest: don't use stringly paths for `compose_and_run`)
 - rust-lang#139614 (Avoid empty identifiers for delegate params and args.)
 - rust-lang#139626 (Remove unnecessary `mut` in test.)
 - rust-lang#139630 (Miri subtree update)

r? `@ghost`
`@rustbot` modify labels: rollup
rust-timer added a commit to rust-lang-ci/rust that referenced this pull request Apr 10, 2025
Rollup merge of rust-lang#139630 - RalfJung:miri-sync, r=RalfJung

Miri subtree update

r? `@ghost`

a sync is needed to fix the miri-test-libstd failures
@bors bors merged commit c9613f8 into rust-lang:master Apr 10, 2025
6 checks passed
@rustbot rustbot added this to the 1.88.0 milestone Apr 10, 2025
@bors
Copy link
Collaborator

bors commented Apr 10, 2025

⌛ Testing commit 955d92f with merge 2205455...

@RalfJung RalfJung deleted the miri-sync branch April 14, 2025 11:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants