Skip to content

Detect mixed-size and mixed-atomicity non-synchronized accesses #6015

Detect mixed-size and mixed-atomicity non-synchronized accesses

Detect mixed-size and mixed-atomicity non-synchronized accesses #6015

Triggered via pull request October 23, 2023 10:32
Status Failure
Total duration 28m 36s
Artifacts

ci.yml

on: pull_request
Matrix: build
bors build finished
0s
bors build finished
bors build finished
0s
bors build finished
cronjob failure notification
0s
cronjob failure notification
Fit to window
Zoom out
Zoom in

Annotations

12 errors
test generated output: tests/pass-dep/concurrency/linux-futex.rs#L1
you likely need to bless the tests with `./miri test --bless`
Unmatched diagnostics: tests/pass-dep/concurrency/linux-futex.rs#L139
Error: Undefined Behavior: Data race detected between (1) Read on thread `main` and (2) Read on thread `<unnamed>` at alloc1. (2) just happened here
build (ubuntu-latest, x86_64-unknown-linux-gnu)
Process completed with exit code 1.
test generated output: tests/pass-dep/concurrency/linux-futex.rs#L1
you likely need to bless the tests with `./miri test --bless`
Unmatched diagnostics: tests/pass-dep/concurrency/linux-futex.rs#L139
Error: Undefined Behavior: Data race detected between (1) Read on thread `main` and (2) Read on thread `<unnamed>` at alloc1. (2) just happened here
build (macos-latest, x86_64-apple-darwin)
Process completed with exit code 1.
test generated output: tests/pass-dep/concurrency/linux-futex.rs#L1
you likely need to bless the tests with `./miri test --bless`
Unmatched diagnostics: tests/pass-dep/concurrency/linux-futex.rs#L139
Error: Undefined Behavior: Data race detected between (1) Read on thread `main` and (2) Read on thread `<unnamed>` at alloc1. (2) just happened here
build (windows-latest, i686-pc-windows-msvc)
Process completed with exit code 1.