Skip to content

Conversation

RalfJung
Copy link
Member

@RalfJung RalfJung commented May 5, 2025

r? @ghost

geetanshjuneja and others added 30 commits April 29, 2025 19:38
move EnvVars::cleanup into the main-thread-exit handler
add -Zmiri-deterministic-concurrency flag and use it for concurrency tests
TB: add `Cell` state to support more fine-grained tracking of interior mutable data
…ctional).

- Add a cargo feature to enable GenMC support (off by default)
- Add support for GenMC datastructures to MiriMachine
- Adjust several functions where GenMC needs to be informed about relevant events (e.g., atomic accesses)
- Add skeleton code for parsing GenMC command line arguments
- Some cleanup
  - Finish sentences with a `.`
  - Fix some spelling errors/typos

Co-authored-by: Ralf Jung <post@ralfj.de>
Previously, the pointee type would be behind a `*const` pointer, so
`ty_is_freeze` would always be `true`, even if there was an
`UnsafeCell` in `Box`.
…e-box

Tree Borrows: Correctly handle interior mutable data in `Box`
move tests that are identical between SB and TB to shared files
alloc_addresses: when we are running out of addresses, start reusing more aggressively
@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label May 5, 2025
@rustbot
Copy link
Collaborator

rustbot commented May 5, 2025

The Miri subtree was changed

cc @rust-lang/miri

@RalfJung
Copy link
Member Author

RalfJung commented May 5, 2025

@bors r+ p=1

@bors
Copy link
Collaborator

bors commented May 5, 2025

📌 Commit 4b8f88b 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 May 5, 2025
@bors
Copy link
Collaborator

bors commented May 5, 2025

⌛ Testing commit 4b8f88b with merge 2e6882a...

@bors
Copy link
Collaborator

bors commented May 5, 2025

☀️ Test successful - checks-actions
Approved by: RalfJung
Pushing 2e6882a to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label May 5, 2025
@bors bors merged commit 2e6882a into rust-lang:master May 5, 2025
7 checks passed
@rustbot rustbot added this to the 1.88.0 milestone May 5, 2025
Copy link
Contributor

github-actions bot commented May 5, 2025

What is this? This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 0f73f0f (parent) -> 2e6882a (this PR)

Test differences

No test diffs found

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 2e6882ac5be27a73293d6f7ae56397fdf32848de --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. dist-apple-various: 5546.5s -> 7676.3s (38.4%)
  2. dist-powerpc64-linux: 6595.4s -> 5466.8s (-17.1%)
  3. dist-x86_64-apple: 9796.2s -> 8612.8s (-12.1%)
  4. dist-aarch64-apple: 6035.7s -> 5426.0s (-10.1%)
  5. x86_64-gnu-llvm-20-3: 7369.4s -> 6648.0s (-9.8%)
  6. aarch64-apple: 3488.1s -> 3266.3s (-6.4%)
  7. x86_64-msvc-ext2: 6083.7s -> 5709.1s (-6.2%)
  8. x86_64-apple-2: 1265.8s -> 1343.2s (6.1%)
  9. dist-x86_64-netbsd: 5018.7s -> 5315.7s (5.9%)
  10. x86_64-apple-1: 5803.6s -> 5516.2s (-5.0%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (2e6882a): comparison URL.

Overall result: ❌ regressions - no action needed

@rustbot label: -perf-regression

Instruction count

This is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.

mean range count
Regressions ❌
(primary)
0.4% [0.4%, 0.4%] 1
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.4% [0.4%, 0.4%] 1

Max RSS (memory usage)

Results (primary 0.0%)

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.

mean range count
Regressions ❌
(primary)
0.6% [0.4%, 0.9%] 8
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-0.7% [-1.1%, -0.4%] 6
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.0% [-1.1%, 0.9%] 14

Cycles

Results (primary -0.4%)

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.

mean range count
Regressions ❌
(primary)
0.5% [0.4%, 0.5%] 3
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-0.7% [-1.0%, -0.4%] 8
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) -0.4% [-1.0%, 0.5%] 11

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 770.361s -> 770.068s (-0.04%)
Artifact size: 365.46 MiB -> 365.41 MiB (-0.02%)

@RalfJung RalfJung deleted the miri-sync branch May 8, 2025 17:49
@zetanumbers
Copy link
Contributor

Seems like this update introduced what seems to me a regression for my library's example in https://github.com/zetanumbers/scope-lock when running inside of interpreter. Trying to bisect this issue further.

@RalfJung
Copy link
Member Author

Please file an issue. This PR only changes Miri, so seeing a regression outside of Miri should be impossible. If you see a regression inside Miri, it might also be Miri now finding UB that it missed before.

@zetanumbers
Copy link
Contributor

rust-lang/miri#4321

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merged-by-bors This PR was explicitly merged by bors. 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.

9 participants