Detect mixed-size and mixed-atomicity non-synchronized accesses #6015
ci.yml
on: pull_request
Matrix: build
style checks
2m 3s
bors build finished
0s
bors build finished
0s
cronjob failure notification
0s
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.
|