You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have Mocha tests that have started to break in Node.js 0.10.0 with the following message:
(node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.
util.js:35
var str = String(f).replace(formatRegExp, function(x) {
^
RangeError: Maximum call stack size exceeded
The initial "process.nextTick" warning is repeated many times, as one might expect from the recursion.
I'm having a very hard time isolating a minimal test case. It only seems to trigger under a certain combination of test files, but removing tests at random "fixes" the problem. It seems like I can still trigger the problem even if I modify my tests to be empty (i.e., none of my own code is being run, just the BDD "describe" and "it" calls).
As soon as I can get something minimal, I'll add it here.
Update: The following single-file test suite will trigger the bug.
I have Mocha tests that have started to break in Node.js 0.10.0 with the following message:
The initial "process.nextTick" warning is repeated many times, as one might expect from the recursion.
I'm having a very hard time isolating a minimal test case. It only seems to trigger under a certain combination of test files, but removing tests at random "fixes" the problem. It seems like I can still trigger the problem even if I modify my tests to be empty (i.e., none of my own code is being run, just the BDD "describe" and "it" calls).
As soon as I can get something minimal, I'll add it here.
Update: The following single-file test suite will trigger the bug.
https://gist.github.com/tomxtobin/5173183
The text was updated successfully, but these errors were encountered: