-
-
Notifications
You must be signed in to change notification settings - Fork 91
-
-
Notifications
You must be signed in to change notification settings - Fork 91
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
Mocha not spawned due to long argument list? #154
Comments
It seems to be an OS issue: Windows has a strong limit on the maximum length of a path (see: Maximum Path Length Limitation). So you should check that your paths are not too long for this OS. Or you could try to increase this limit :
|
Hmm I was suspecting it to be Windows. Too bad I'm still on version 1511... And having to set registry keys to run the tests is not something friendly for the other developers. In one of the tools we've been developing as a developer aid, we started mocha in a forked process and are using messages to send over the files to test (see: https://github.com/AFASResearch/typescript-assistant/blob/master/src/testing/mocha.ts#L68). This might be a nice solution for gulp-mocha as well? |
It could also be an issue with the maximum length of a command : as for paths, Windows is very limited (8191 characters) comparing to Linux systems (usually 131072 characters). |
Have the same issue on Windows 10, is the any way to pass a pattern?
|
On Windows 10, get same problem. Reverting back to |
Same issue here, why wouldn't this have been an issue in previous versions? |
@gingur In previous versions, this package called the Mocha API directly (EDIT: but it seems that this API has some severe issues). So, we hadn't any problem as the JavaScript API has no such limitations on Windows. The v4 spawns instead the Mocha executable: the operating system limitations applies now. |
@cedx understood, we've reverted our dependency back down to |
Not the best solution, but personally, I ended up by no longer using the Gulp plugin and calling directly the Mocha executable. For example: https://github.com/cedx/which.js/blob/master/gulpfile.js#L59 The OS limitations still applies... but the new way launches all my tests without using a long Shell command (like the one built by the plugin). So the issue is partially resolved on my side. |
With version 4, when trying to use gulp-mocha, I'm getting
It seems this is related to the passing of the files argument, which is quite large in our case (500+ entries).
Environment: Windows 10
The text was updated successfully, but these errors were encountered: