Skip to content

Commit 9ab9b6e

Browse files
committed
update readme
1 parent 7a97db0 commit 9ab9b6e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
1-
This repository serves to run the libcore and liballoc unit test suites in [Miri](https://github.com/rust-lang/miri/): we basically run `cargo miri test` against [coretests](https://github.com/rust-lang/rust/tree/master/library/core/tests), [alloctests](https://github.com/rust-lang/rust/tree/master/library/alloc/tests) and [liballoc itself](https://github.com/rust-lang/rust/tree/master/library/alloc) (there do not seem to be `#[test]` functions embedded in libcore).
1+
This repository serves to run the libcore, liballoc, and libstd test suites in [Miri](https://github.com/rust-lang/miri/).
2+
This includes unit tests, integration tests, and doc tests, but not rustc ui tests.
23

3-
Every night, a Travis cron job runs the tests against the latest nightly, to make sure we notice when changes in Rust or Miri break a test.
4-
5-
You can also run the libstd test suites, but note that large parts of them will fail due to relying on platform-specific APIs that Miri does not implement.
4+
Every night, a CI cron job runs the tests against the latest nightly, to make sure we notice when changes in Rust or Miri break a test.
5+
(Some libstd tests are excluded since they rely on platform-specific APIs that Miri does not implement.)
66

77
### Running the tests yourself
88

0 commit comments

Comments
 (0)