Open tbeckley opened 2 weeks ago
Unwinding on panics isn't supported yet. Because of this libtest is unable to catch the test failure and show the test result it saved. Instead the process is aborted. Try using RUSTFLAGS="-Cpanic=abort -Zpanic-abort-tests"
which will make libtest handle panic=abort correctly by running each test in a new subprocess. Be aware however that spawning processes is relatively slow on Windows.
That works perfectly! Sorry for the dumb question and thank you for the quick response! I hadn't actually considered that the test fail causes a panic...
Hi guys,
Apologies if this is a dupe, I searched but couldn't find anything. Big GUI project here and have been playing around with using cranelift to improve compile times. When running my tests on windows, any failing
assert_eq!()
will trigger nonsensical error messages as opposed to the correct error message about a failing assertion. Minimal example:cargo.toml:
Error message when using cranelift:
And without cranelift:
I've also seen errors for memory access violation and stack overflows.
Result of
rustup show
: