-
Notifications
You must be signed in to change notification settings - Fork 854
Closed
Labels
FrozenDueToAgeNeedsFixThe path to resolution is known, but the work has not been done.The path to resolution is known, but the work has not been done.
Milestone
Description
The Github actions workflows in this repo currently fail for the Windows runs, even when the corresponding Ubuntu runs work as expected. It looks like this has been the case for awhile - should these tests be removed if not needed, or fixed if they are expected to be working? I was experimenting with some changes in a fork and it prevents surfacing of issues that may have been introduced by a change.
Stack trace:
Error: spawn UNKNOWN
at ChildProcess.spawn (node:internal/child_process:414:11)
at Object.spawn (node:child_process:761:9)
at D:\a\vscode-go\vscode-go\node_modules\@vscode\test-electron\out\runTest.js:63:24
at new Promise (<anonymous>)
at innerRunTests (D:\a\vscode-go\vscode-go\node_modules\@vscode\test-electron\out\runTest.js:61:12)
at runTests (D:\a\vscode-go\vscode-go\node_modules\@vscode\test-electron\out\runTest.js:42:12)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async main (D:\a\vscode-go\vscode-go\out\test\runTest.js:63:5) {
errno: -4094,
code: 'UNKNOWN',
syscall: 'spawn'
}
History of failed runs:
https://github.com/golang/vscode-go/actions/workflows/test-long.yml
Metadata
Metadata
Assignees
Labels
FrozenDueToAgeNeedsFixThe path to resolution is known, but the work has not been done.The path to resolution is known, but the work has not been done.