At https://github.com/RalfJung/miri-test-libstd/, I have set things up such that one can run the libcore and liballoc test suite against Miri. The basic idea is to have a Cargo.toml file like this (very close to the normal one for libcore):
[package]
authors = ["The Rust Project Developers"]
name = "core_miri_test"
version = "0.0.0"
autotests = false
autobenches = false
edition = "2018"
[lib]
name = "core_miri_test"
path = "../libcore/lib.rs"
test = false
bench = false
[[test]]
name = "coretests"
path = "../libcore/tests/lib.rs"
[dev-dependencies]
rand = "0.7"
Then I make ../libcore a symlink to the actual libcore sources, cd into the dir with the above Cargo.toml, and run cargo miri test. This worked fine until recently (until nightly-2019-10-17, to be precise).
error[E0658]: associated type bounds are unstable
--> core_miri_test/../libcore/pin.rs:445:15
|
445 | impl<P: Deref<Target: Unpin>> Pin<P> {
| ^^^^^^^^^^^^^
|
= note: for more information, see https://github.com/rust-lang/rust/issues/52662
= help: add `#![feature(associated_type_bounds)]` to the crate attributes to enable
error[E0658]: associated type bounds are unstable
--> core_miri_test/../libcore/pin.rs:754:18
|
754 | impl<P: DerefMut<Target: Unpin>> DerefMut for Pin<P> {
| ^^^^^^^^^^^^^
|
= note: for more information, see https://github.com/rust-lang/rust/issues/52662
= help: add `#![feature(associated_type_bounds)]` to the crate attributes to enable
I tried adding these feature gates to every crate root I could think of (the lib.rs of both libcore and its test crate), but the errors are sticking. Unfortunately the error doesn't tell me which file it thinks is the crate root.
Any idea what this could be caused by? Until this is fixed, we won't have Miri coverage of the libcore and liballoc test suite.
https://github.com/rust-lang/rust/pull/66004 fixed the original issue; now this tracks re-landing those checks (possibly after some transition period).
Original issue
At https://github.com/RalfJung/miri-test-libstd/, I have set things up such that one can run the libcore and liballoc test suite against Miri. The basic idea is to have a
Cargo.tomlfile like this (very close to the normal one for libcore):Then I make
../libcorea symlink to the actual libcore sources, cd into the dir with the aboveCargo.toml, and runcargo miri test. This worked fine until recently (until nightly-2019-10-17, to be precise).But since then something broke, and now I get lots of build failures:
I tried adding these feature gates to every crate root I could think of (the
lib.rsof both libcore and its test crate), but the errors are sticking. Unfortunately the error doesn't tell me which file it thinks is the crate root.Any idea what this could be caused by? Until this is fixed, we won't have Miri coverage of the libcore and liballoc test suite.