-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Miri subtree update #141860
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
Miri subtree update #141860
Conversation
Automatic Rustup
./miri bench: sort results alphabetically
test some aarch64 windows targets
fix zulip topic URL
Automatic Rustup
Automatic Rustup
Support F_GETFL and F_SETFL for fcntl
attempt to fix squash on Windows
Automatic Rustup
Implement file cloning on Windows
fix comment in before_stack_pop
Automatic Rustup
Remove useless file
Automatic Rustup
The test did `write` and `read` and hoped that it would read/write everything, which doesn't always happen and caused CI failures. Switch to `write_all` and `read_to_end` to make it more reliable.
…-a-lot-instead Fix tokio/file-io.rs test relying on `read`/`write` not being short
Tokio `AsyncWriteExt::write` doesn't actually ensure that the contents have written, it just *starts* the write operation. To ensure that the file has actually been written, we need to `sync_all` first.
The Miri subtree was changed cc @rust-lang/miri |
@bors r+ p=10 |
☀️ Test successful - checks-actions |
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 9b0268a (parent) -> a88fc0e (this PR) Test differencesShow 33470 test diffsStage 1
Stage 2
(and 16656 additional test diffs) Additionally, 16714 doctest diffs were found. These are ignored, as they are noisy. Job group index Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard a88fc0eaae4551f840d35d88f77105b535cf7912 --output-dir test-dashboard And then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
Finished benchmarking commit (a88fc0e): comparison URL. Overall result: ❌ regressions - please read the text belowOur benchmarks found a performance regression caused by this PR. Next Steps:
@rustbot label: +perf-regression Instruction countThis 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.
Max RSS (memory usage)Results (primary 3.4%, secondary 1.1%)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.
CyclesResults (primary 2.8%, secondary -0.2%)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.
Binary sizeResults (primary 1.1%)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.
Bootstrap: 775.511s -> 775.166s (-0.04%) |
Looks like spurious on both affected results -- dropping regression label. |
r? @ghost
Includes rust-lang/miri#4370 to unbreak PR CI. (So we're committing to having bda28aa38 in the Miri history by landing this, whether or not that Miri PR lands.)
Cc @Noratrieb @tiif