microsoft / microsoft/vscode-test
Error using VS Code insders on macOS runners
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 316
- Forks
- 73
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
I am using the following configuration of .vscode-test.mjs which uses the insiders version.
import { defineConfig } from "@vscode/test-cli";
export default defineConfig({
files: "out/test/**/*.test.js",
version: "insiders",
mocha: {
retries: 5,
parallel: false,
},
});
I execute the tests in a macos-latest pipeline via vscode-test script. I also tried to execute the tests executing in a macos-15 pipeline to validate it is not a macOS problem.
In both pipelines I get the following output:
> vscode-test
- Resolving version...
✔ Validated version: insiders
- Found at https://update.code.visualstudio.com/latest/darwin-arm64/insider?released=true
✔ Found at https://update.code.visualstudio.com/latest/darwin-arm64/insider?released=true
- Downloading (299.92 MB)
✔ Downloaded VS Code (07b4ff1883f94da91f6d698744fc7c3638b59720) into /Users/runner/work/vscode-logging/vscode-logging/.vscode-test/vscode-darwin-arm64-insiders
Test error: Error: spawn /Users/runner/work/vscode-logging/vscode-logging/.vscode-test/vscode-darwin-arm64-insiders/Visual Studio Code - Insiders.app/Contents/MacOS/Electron ENOENT
Exit code: -2
Error: Process completed with exit code 1.
This makes it impossible to execute any tests on macOS with the insiders version.
The stable version does currently work, but I don't know if this issue will roll over to the next stable.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the .vscode-test.mjs configuration and the macOS pipeline that runs the vscode-test script. Reproduce the insiders download, then inspect the downloaded application path and the spawn failure shown in the logs. Done means the insiders version launches and the extension tests complete successfully on macOS runners.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100