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
This might be a recent regression because I do not remember seeing it in older versions. Is more likely to happen if the download fails or is interrupted but the main issue is that extest fails to use the mentioned folder for temporary files, polluting the codebase.
Due to the nature of the filenames is also dangerous to add a vscode* entry to .gitignore.
Steps to reproduce
Interrupt extester while is downloading vscode, even if you mentioned `-s some/temp/folder` on the command you passed to it.
Logs
drwxr-xr-x 1 ssbarnea ssbarnea 96 Dec 24 11:28 vscodeG6Qa55
drwxr-xr-x 1 ssbarnea ssbarnea 96 Dec 24 11:05 vscodeIJZ3bk
drwxr-xr-x 1 ssbarnea ssbarnea 96 Dec 24 11:09 vscodeNc1Kf6
Operating System
MacOS and Ubuntu
Visual Studio Code
vscode-extension-tester
8.10.0
NodeJS
v20.18.0
npm
10.8.2
The text was updated successfully, but these errors were encountered:
Describe the bug
This might be a recent regression because I do not remember seeing it in older versions. Is more likely to happen if the download fails or is interrupted but the main issue is that extest fails to use the mentioned folder for temporary files, polluting the codebase.
Due to the nature of the filenames is also dangerous to add a
vscode*
entry to.gitignore
.Steps to reproduce
Logs
Operating System
MacOS and Ubuntu
Visual Studio Code
vscode-extension-tester
8.10.0
NodeJS
v20.18.0
npm
10.8.2
The text was updated successfully, but these errors were encountered: