`npm run test` fails when run from both win10 and wsl

Environment data

• VS Code version: 1.43.2
• Extension version (available under the Extensions sidebar): 2020.4.0-dev
• OS and version: Windows 10 - 1903
• Python version (& distribution if applicable, e.g. Anaconda): 3.8 but not relevant
• Type of virtual environment used (N/A | venv | virtualenv | conda | …):
• Relevant/affected Python packages and their versions:
• Relevant/affected Python-related VS Code extensions and their versions:
• Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977):
• Value of the python.languageServer setting:

Expected behaviour

npm run test successfully runs when the command is issued in win10. When the command is rerun in WSL, the script only checks for the presence of ./.vscode-test/vscode-[ver].

However, the installer places the downloaded copy for windows and the copy needed for WSL in different locations. So it skips installing the extra version it needs, and subsequently crashes.

This is also happens in reverse (I.E. wsl successfully runs and then the command is run from win10)

Actual behaviour

root @ win10 .../projects/all_msft/vscode-python 19:22 0
@In [2] $ npm run test

> python@2020.4.0-dev test /mnt/c/Users/fac/projects/all_msft/vscode-python
> node ./out/test/standardTest.js && node ./out/test/multiRootTest.js

****************************************************************************************************
Start Standard tests
Found .vscode-test/vscode-1.43.2. Skipping download.
Test error: Error: spawn /mnt/c/Users/fac/projects/all_msft/vscode-python/.vscode-test/vscode-1.43.2/VSCode-linux-x64/code ENOENT
Exit code:   -2
Done

End Standard tests (with errors) Failed
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! python@2020.4.0-dev test: `node ./out/test/standardTest.js && node ./out/test/multiRootTest.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the python@2020.4.0-dev test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-03-26T23_22_08_810Z-debug.log

Sorry if anything here is unclear at all. I’d be happy to elaborate if so.

[ericsnowcurrently]

@farisachugthai, thanks for the update. I’m going to mark this issue as an enhancement request and we’ll make a decision in the near future on whether to proceed with it. Thanks again.

[luabud]

Thanks for the suggestion! We talked about it with the team and we have unfortunately decided we will not be moving forward with this idea. We think there isn’t an enough widespread need for this to warrant the maintenance cost for the feature.