Home → Problems →

Help with diagnosing error when running npm test (github)

• Edit

peter hull

21 Nov, 2023 09:13 AM

Hi, I've got an appveyor job running for a github project (which is not updated very often) and it has failed the last few times.

https://github.com/pedro-w/vscode-tmlanguage

https://ci.appveyor.com/project/pedro-w/vscode-tmlanguage/builds/48...

The triggers have been a change to README and adding a tag which I would not expect to be the kind of change to cause a build failure. What I see is (cleaned up a bit)

npm test
> tmlanguage@1.0.0 pretest
> tsc -p ./
> tmlanguage@1.0.0 test
> ts-standard && node ./out/test/runTest.js
Downloading VS Code 1.84.2 from https://update.code.visualstudio.com/1.84.2/win32-x64-archive/stable
Downloading VS Code (132316958B)
Downloaded VS Code into C:\projects\vscode-tmlanguage\.vscode-test\vscode-win32-x64-archive-1.84.2
Exit code:   3221225785
Failed
Failures when running tests
Command exited with code 1

Code 3221225785 (aka 0xc0000139) is "STATUS_ENTRYPOINT_NOT_FOUND" I believe.

Running npm test succeeds locally - after the download the npm test script runs

Can you give me some guidance on how to diagnose this?

1. Support Staff 1 Posted by Owen McDonnell on 29 Nov, 2023 10:15 PM

   

   Are you sure there isn't more than a different readme between branches?
   This build uses VSCode 1.81.1, while this one uses 1.84.2.

   • Edit

2. 2 Posted by Peter Hull on 01 Dec, 2023 09:40 AM

   

   That's a good point. If you look at
   https://ci.appveyor.com/project/pedro-w/vscode-tmlanguage/builds/47800282 (build 1.0.70 - passes)
   and
   https://ci.appveyor.com/project/pedro-w/vscode-tmlanguage/builds/48574959 (build 1.0.75 - fails)
   They are based on the exact same checkout, e26976a4653586655c03c23f416ead4f43c00a46
   The only difference, as you say, is the version of vscode. (correct me if I'm wrong)
   I'm not asking for a specific version of vscode, it's just the vsce test process downloads whatever is the latest, I believe.
   So this is suggesting to me that there is some mismatch between vscode versions. Is there any way to get any more verbose debug info from the build? As I said, running the same npm test succeeds locally with vscode 1.84.2

   Thanks for your help, much appreciated!

   ________________________________

   • Edit