-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Node stack traces truncated #2770
Comments
Followup: this is not a mocha bug. This is a babel bug -- or at a minimum an area that really could use some improvement in Babel. One thing I didn't mention here is my After some painful debugging I found the entry point of the v8 crash in 'babel-register' apparently caches data about files it compiles by default, and saves them to a file. From looking at My I still don't know why the stack traces get truncated. Bug reportl: babel/babel#5667 |
Thanks for sharing your findings! :) |
Was happening on our CI server and failing all the builds, thanks for sharing this |
I think this is a Mocha problem but it's hard to say, since I don't have anything to compare to, though it could be a general environmental problem. We are getting out of memory errors on a large test suite. I've researched this a lot, and it seems it could be one of several things, but at this point it's very difficult to troubleshoot because I can't get a full stack trace.
Node@6.9.5, mocha@3.2.0
As you can see it's truncating it. I've tried everything I can think of, but none of the
node
command line options have any effect, e.g.node --stack_trace_limit=1000 --max_stack_trace_source_length=1000 ./node_modules/mocha/bin/_mocha ./test --full-trace
I looked at all the v8 options with
stack
here:node --v8-options | grep -B0 -A1 stack
.. and didn't see any others that might be related. Thoughts?
The text was updated successfully, but these errors were encountered: