-
Notifications
You must be signed in to change notification settings - Fork 0
Issues found so far #12
Comments
For several targets like arm, aarch64, mips, when running the unit tests of the
But if I run If I want to turn the test green, I'll have to skip these tests on these targets. But Rust test runner doesn't provide a way to ignore tests via command line arguments. My options:
I like the first option best. |
FWIW, I additionally tested reducing the number of tests that libtest uses for each unit tests from 2 to 1 (as implemented in rust-lang/rust#36339). But that didn't reduce the number of failures. Probably because each unit tests, itself, spawns a bunch of threads. |
👍
Note that this flexibility would also allow running tests on BSD platforms as well, so may have other added benefits! From doing it in libc, though, it's super complicated. |
qemu-ppc64le
doesn't work. Invalid instruction even with the simplest C program.i586-unknown-linux-gnu
:catch_unwind
doesn't work. i686-musl + catch_unwind = fatal runtime error: failed to initiate panic, error 5 rust-lang/rust#35599libc-test
doesn't pass. Assorted libc-test failures rust-lang/libc#357The text was updated successfully, but these errors were encountered: