-
Notifications
You must be signed in to change notification settings - Fork 52
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
ENAMETOOLONG when running unit tests on Windows #420
Comments
Looks like it’s exceeding the command line length limit of Windows. Should see if we can use shorter commands to execute a specified test suite or all tests. Or, more generally, support argument file in XCTest (not sure if we can do this without patching the macOS side). |
Apparently ENAMETOOLONG is a Node error and happens when the pathname is longer than PATH_MAX characters, but that doesn't make sense here, unless it has decided that the test list is a path name. Anyway if all tests are run I guess I can run without the test list in the command line |
According to microsoft/vscode#98514 (comment), |
I think that @stevapple is correct here - this likely does indicate that the command line is exceeding its limit. Trimming the command line, if possible, would be good. A response file approach would be great, but I agree that is a much more difficult proposition. |
@svanimpe can you do a couple of tests for me. Go into the swift argument parser folder and then type
and secondly type
The first should run all tests and the second should run all the tests in test class I guess while you are at it you could also try
|
@adam-fowler @svanimpe Before running these tests you should set the environment for path C:\Library\Developer\Platforms\Windows.platform\Developer\Library\XCTest-development\usr\bin64;%Path% |
@adam-fowler The output of these command is as follows:
Note that I had to run these in Command Prompt, as PowerShell didn't know what to do with the |
Fixed and released in v0.8.2 |
Environment
To Reproduce
This prints the following:
This doesn't happen on Linux.
The diagnostics output is as follows:
The text was updated successfully, but these errors were encountered: