Closed me-rsharma closed 5 months ago
We are seeing the same issues with our insiders tests in CI. Not really sure what is causing them because all stable
tests are running. Any tips or contributions are welcome!
Are either of you still having this problem? Have you managed to work around it?
The root cause of the problem is the binary
path returned by @vscode/test-electron
does not exist. Here's an example from the original logs:
'wdio:vscodeOptions': {
binary: '.../.wdio-vscode-service/vscode-darwin-arm64-1.81.0/Visual Studio Code.app/Contents/MacOS/Electron'
If you inspect the cache you'll find that the Visual Studio Code.app directory was not created. Instead, the path on disk is:
- .../.wdio-vscode-service/vscode-darwin-arm64-1.81.0/Visual Studio Code.app/Contents/MacOS/Electron
+ .../.wdio-vscode-service/vscode-darwin-arm64-1.81.0/Contents/MacOS/Electron
The code responsible is managed by @vscode/test-electron
. The issue appears to have been fixed in v2.3.8 by https://github.com/microsoft/vscode-test/issues/246. If you are unable to update the dependencies, work around the issue by setting the binary
path yourself.
It looks like this was the same as #78 (Open Issue) and #98 (Closed PR). Thanks for fix this in 5.2.3 @christian-bromann. :1st_place_medal:
Hello Team, we are getting another issue when we are trying to run test in
{ browserName: 'vscode', browserVersion: process.env.VSCODE_VERSION || 'stable' }
Logs:
The same test cases is running fine when I am using
Steps to reproduce:
npm install
npm run test:e2e
I have tried different version of vscode
latest
,1.81.0
,1.80.0
,1.71.0
and getting the same error on all these versions