-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Adding --noStackTrace
#985
Comments
I'll fix this for the next version of Jest :) |
Going to close this out in favor of the pull request. The new Jest release will come out soon. |
Summary: The reporting code is a huge mess. This simplifies a bunch of things and makes everything go through the same code path and makes `noStackTrace` work again which hasn't worked properly for maybe half a year. Fixes included: * When a single test is run and it throws a runtime error, we now show the "1 test suite failed" message. * Runtime errors, string errors and error objects thrown in tests now all render the same way and go through a single code path. * Stack trace printing can be disabled with `--noStackTrace` yay, regex Fixes #985. bypass-lint Closes #997 Reviewed By: dmitriiabramov Differential Revision: D3292096 fbshipit-source-id: bb4ce5cb2721327f701c86681c441df98fd57f28
Hi, it seems I am still experiencing the issue. Here is an abridged log that I am receiving to highlight that the stack trace is present in the output:
The error and stack matters little in my case, since I am running a sanity check on my build. But since I am trying to debug, the output of the whole stack and code hides what I am looking for. My cli command is: Jest version: 25.5.4 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
It appears that adding
--noStackTrace
does not suppress the stack trace - at least I presume I should not get so much output when using this feature. Sometimes I get over 100 lines of logging, which puts the details of the failing test off my screen - so I'm interested in reducing the noise somehow.Details
"jest-cli": "^12.0.2"
from
package.json
:from
.babelrc
:The text was updated successfully, but these errors were encountered: