microsoft / microsoft/vscode-test
Hangs on Mac mini M2 headless
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 316
- Forks
- 73
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
I am running tests for a VS Code extension on a self-hosted Github runner.
The runner is installed on an Mac mini M2 ARM architecture. The Mac has a display connected, but no user is logged in during the test. I also don't want to connect a display for productive usage.
Run coactions/setup-xvfb@v1
/opt/homebrew/bin/npm test
> new_ext@0.1.1 test
> npm run compile && npm run test:compile && vscode-test --timeout=5000
> new_ext@0.1.1 compile
> npm run check-types && node esbuild.mjs
> new_ext@0.1.1 check-types
> tsc --noEmit
[watch] build started
[watch] build finished
> new_ext@0.1.1 test:compile
> node esbuild-tests.mjs
- Resolving version...
✔ Validated version: 1.95.1
- Found at https://update.code.visualstudio.com/1.95.1/darwin-arm64/stable?released=true
✔ Found at https://update.code.visualstudio.com/1.95.1/darwin-arm64/stable?released=true
- Downloading (128.81 MB)
✔ Downloaded VS Code into /Users/gh-runner/actions-runner-3/_work/new_ext/new_ext/vscode/.vscode-test/vscode-darwin-arm64-1.95.1
2024-11-05 14:49:18.393 Electron[6385:33271] +[NSXPCSharedListener endpointForReply:withListenerName:replyErrorCode:]: an error occurred while attempting to obtain endpoint for listener 'ClientCallsAuxiliary': Connection interrupted
It hangs at this step for a couple of minutes until the Github action times out.
Any clue what's wrong?
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 npm test scripts, esbuild.mjs, esbuild-tests.mjs, and the vscode-test invocation shown in the report. Reproduce the Electron launch on a headless macOS ARM self-hosted runner after setup-xvfb runs, then inspect the hang around the ClientCallsAuxiliary message. Done means the VS Code extension tests complete without hanging or timing out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, github-actions, macos, typescript, vscode
- Domain
- ci-cd, desktop, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100