-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rust 1.33.0 failing UI tests when run with single core #59122
Comments
I've managed to confirm that the issue occurs when the compiler is built with What is the process for creating the vendor directory when creating a source tarball of the compiler? Are there any tests that verify the right dependencies were vendored in? |
Aha! I turns out it's not a vendoring issue, but rather a number of test threads issue! I was able to reproduce without vendoring, but by invoking the test suite with a single core: ./x.py test -vv -j1 src/test/run-fail # fails the two test cases above
./x.py test -vv src/test/run-fail # succeeds |
libtest: run all tests in their own thread, if supported by the host This reverts the threading changes of rust-lang/rust#56243, which made it so that with `-j1`, the test harness does not spawn any threads. Those changes were done to enable Miri to run the test harness, but Miri supports threads nowadays, so this is no longer needed. Using a thread for each test is useful because the thread's name can be set to the test's name which makes panic messages consistent between `-j1` and `-j2` runs and also a bit more readable. I did not revert the HashMap changes of rust-lang/rust#56243; using a deterministic map seems fine for the test harness and the more deterministic testing is the better. Fixes rust-lang/rust#59122 Fixes rust-lang/rust#70492
I'm trying to package/build Rust 1.33.0 on Guix and I'm consistently getting some test failures regarding panic messages.
Several run-fail tests check that a
#[test]
with a name liketest_foo
prints a message likethread 'test_foo' panicked...
, but instead the output will come out asthread 'main' panicked...
.I'm not really sure what can be the cause of the issue, but FWIW we build Rust with the previous stable version already packaged in Guix, and we'll link to our packaged versions of llvm and jemalloc.
Happy to provide more details as needed; log from the failing test cases is below
The text was updated successfully, but these errors were encountered: