REditorSupport / REditorSupport/vscode-R

CI for macOS and windows always fails

Open
#1,521 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug engineering
Dominant language
TypeScript
Stars
1.2k
Forks
139
Avg merge
2h 46m
Merged PRs (30d)
5

Description

Describe the bug
mac and windows test runners always fail for all PRs, no matter if the PR in question has no issues with it. The failure is because the runners are crashing, which cancels all other test runners in the process.

Details
Run GabrielBB/xvfb-action@v1.0
/Users/runner/hostedtoolcache/node/16.20.1/arm64/bin/npm run test

> r@2.8.2 pretest
> tsc -p ./


> r@2.8.2 test
> node ./out/test/runTest.js

Downloading VS Code 1.89.0 from https://update.code.visualstudio.com/1.89.0/darwin-arm64/stable
Downloading VS Code (130895428B)
Downloading VS Code [------------------------------] 3%Downloading VS Code [=-----------------------------] 6%Downloading VS Code [===---------------------------] 10%Downloading VS Code [====--------------------------] 14%Downloading VS Code [=====-------------------------] 17%Downloading VS Code [======------------------------] 21%Downloading VS Code [=======-----------------------] 25%Downloading VS Code [========----------------------] 28%Downloading VS Code [=========---------------------] 32%Downloading VS Code [==========--------------------] 36%Downloading VS Code [============------------------] 41%Downloading VS Code [==============----------------] 47%Downloading VS Code [===============---------------] 51%Downloading VS Code [=================-------------] 57%Downloading VS Code [==================------------] 61%Downloading VS Code [===================-----------] 65%Downloading VS Code [====================----------] 67%Downloading VS Code [=====================---------] 72%Downloading VS Code [=======================-------] 78%Downloading VS Code [========================------] 83%Downloading VS Code [==========================----] 90%Downloading VS Code [============================--] 95%Downloaded VS Code into /Users/runner/work/vscode-R/vscode-R/.vscode-test/vscode-darwin-arm64-1.89.0
Downloaded VS Code into /Users/runner/work/vscode-R/vscode-R/.vscode-test/vscode-darwin-arm64-1.89.0
Test error: Error: spawn /Users/runner/work/vscode-R/vscode-R/.vscode-test/vscode-darwin-arm64-1.89.0/Visual Studio Code.app/Contents/MacOS/Electron ENOENT
Exit code:   -2
Failed to run tests
Error: The process '/Users/runner/hostedtoolcache/node/16.20.1/arm64/bin/npm' failed with exit code 1

Some thoughs:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by examining the CI configuration that runs npm run test on macOS and Windows, then reproduce the failure shown for GabrielBB/xvfb-action@v1.0. Compare the deprecated action with coactions/setup-xvfb and review the Node.js version used by the runners. Done means the macOS and Windows jobs complete successfully without cancelling other test runners.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, node.js, typescript
Domain
ci-cd, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.