EEXIST: file already exists - Workspace an obstacle? about al-test-runner HOT 5 CLOSED

Hi Natalie,

I'm not sure what's happening here. I've built a new version of the app to output some values give us a clue. I'll send you an email.

from al-test-runner.

Hi,

If you are using a workspace with multiple roots then yes, I expect that that is the problem. The extension needs more work to allow you to specify which folder contains the extension with your tests.

I haven't been able to replicate your issue exactly, but I have got some inconsistent results with workspaces. Try dragging the folder that contains your test extension to be first in the workspace, if it isn't already and reloading VS Code.

from al-test-runner.

Switching the folders within the workspance indeed puts the .altestrunner folder into the correct place, however it will still throw an error:

EEXIST: file already exists, mkdir 'PATH\MyRepo\test\.altestrunner'

from al-test-runner.

BTW I've tested to open the test folder seperately in VS Code. But the error persists there, too:

EEXIST: file already exists, mkdir 'PATH\MyRepo\test\.altestrunner'

from al-test-runner.

The EEXIST error message was caused by comments in the launch.json (I had disabled the StartupObject configurations). The issue was not related to workspaces.

Next obstacles solved by:

• If you are running the bash terminal, "Select Default Shell" and choose PowerShell; then "Kill Terminal".
• Open PowerShell as administrator:
  install-module navcontainerhelper or update-module navcontainerhelper
Check-NavContainerHelperPermissions -fix
• in the launch.json, the servername must match exactly the docker container name (no trailing backslash, case sensitive)
• Retry, retry ... until a login window comes, then retry again.

Thanks for your help, James :)

from al-test-runner.