-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
communicate the error when a test fails in release mode #14972
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
Comments
Hello, Sir! 😄 Trying to reproduce this with a fresh zig version compiled from master at 68c7261 without success. I used an init-exe scaffold and replaced default test in My output includes the failing test and error. My output also is generally different than yours which makes me think I a missing some config or flags that you have.
Perhaps I need to make some adjustments to get a proper repro? Let me know what else I can do and in the mean time, I will try a few more things. |
If I had to guess I'd say that you are using an old lib/ directory. If that is the problem, then you either need to delete the lib directory and start using the "no lib" option, or you need to run the install step to copy the lib folder from the zig source tree to your installation prefix where your zig binary lives. |
Extracted from #14647.
Running unit tests via the build system in release mode with a failure currently looks like this:
There is one piece of information that is lost, which is the fact that the test failed with
error.TestUnexpectedResult
. This information could be communicated via the TestResult message over test protocol, or the test runner could simply print the error name to stderr before reporting a failure.The text was updated successfully, but these errors were encountered: