Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some strange behaviour with Windows since last week #9630

Closed
3 of 13 tasks
derberg opened this issue Apr 4, 2024 · 5 comments
Closed
3 of 13 tasks

Some strange behaviour with Windows since last week #9630

derberg opened this issue Apr 4, 2024 · 5 comments
Assignees
Labels
Area: JavaScript and Node.js bug report investigate Collect additional information, like space on disk, other tool incompatibilities etc. OS: Windows

Comments

@derberg
Copy link

derberg commented Apr 4, 2024

Description

Our CI failing because of cache.

Repo: https://github.com/asyncapi/cli

Example:

npm ERR! code EEXIST
npm ERR! syscall open
npm ERR! path C:\npm\cache\_cacache\tmp\076[5](https://github.com/asyncapi/cli/actions/runs/8552018373/job/23432266983?pr=1340#step:8:6)ef1c
npm ERR! errno -4075
npm ERR! EEXIST: file already exists, open 'C:\npm\cache\_cacache\tmp\07[6](https://github.com/asyncapi/cli/actions/runs/8552018373/job/23432266983?pr=1340#step:8:7)5ef1c'
npm ERR! File exists: C:\npm\cache\_cacache\tmp\0[7](https://github.com/asyncapi/cli/actions/runs/8552018373/job/23432266983?pr=1340#step:8:8)65ef1c
npm ERR! Remove the existing file and try again, or run npm
npm ERR! with --force to overwrite files recklessly.

npm ERR! A complete log of this run can be found in: C:\npm\cache\_logs\2024-04-04T0[9](https://github.com/asyncapi/cli/actions/runs/8552018373/job/23432266983?pr=1340#step:8:10)_02_10_952Z-debug-0.log

I tried with windows-latest and windows-2019.

I tried many things already:

    npm install --force

or

    rm -rf C:\npm\cache\_cacache\tmp
    npm cache clean --force
    npm ci

or

    npm ci

super frustrating as it is just not clear what happens. It behaves the same no matter if I use cache through actions/setup-node@v4 or not.

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • macOS 11
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • Windows Server 2019
  • Windows Server 2022

Image version and build link

example issue run: https://github.com/asyncapi/cli/actions/runs/8552018373/job/23432266983?pr=1340

Current runner version: '2.314.1'
Operating System
  Microsoft Windows Server [2](https://github.com/asyncapi/cli/actions/runs/8552018373/job/23432266983?pr=1340#step:1:2)019
  10.0.17763
  Datacenter
Runner Image
  Image: windows-2019
  Version: 20240[3](https://github.com/asyncapi/cli/actions/runs/8552018373/job/23432266983?pr=1340#step:1:3)22.1.0
  Included Software: https://github.com/actions/runner-images/blob/win19/202[4](https://github.com/asyncapi/cli/actions/runs/8552018373/job/23432266983?pr=1340#step:1:4)0322.1/images/windows/Windows2019-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/win19%2F20240322.1
Runner Image Provisioner
  2.0.3[6](https://github.com/asyncapi/cli/actions/runs/8552018373/job/23432266983?pr=1340#step:1:7)1.1

Is it regression?

I don't know when it started

Expected behavior

passing installation

Actual behavior

cache install fails

Repro steps

not sure how you could do it

@shamil-mubarakshin
Copy link
Contributor

Hey @derberg. I believe this PR enabled condition for windows job execution, which hadn't run before. We will have a look

@shamil-mubarakshin shamil-mubarakshin added Area: JavaScript and Node.js OS: Windows investigate Collect additional information, like space on disk, other tool incompatibilities etc. and removed needs triage labels Apr 4, 2024
@derberg
Copy link
Author

derberg commented Apr 4, 2024

changes from https://github.com/asyncapi/cli/pull/1318/files#diff-ef4f20ad9ac611c67466a8f25e69c3924ed476b297b5dd67f54829c012ea3a00 are in majority no longer in place

look at lates changes I do in asyncapi/cli#1340

there is no longer additional checking conditions

@derberg
Copy link
Author

derberg commented Apr 4, 2024

now it is just plain npm ci with no fancy caching

last run with it: https://github.com/asyncapi/cli/actions/runs/8554605501/job/23440268008?pr=1340

@MaksimZhukov
Copy link
Contributor

MaksimZhukov commented Apr 8, 2024

Hello @derberg!
The issue is related to npm and can be mitigated by manually downgrading npm version or specifying Node.js 16 using setup-node action. Please find details in this workflow run and corresponding workflow file. Please file a bug in the npm/cli repository.
Thank you!

@derberg
Copy link
Author

derberg commented Apr 9, 2024

@MaksimZhukov thanks for taking time to look into it 🙏🏼

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: JavaScript and Node.js bug report investigate Collect additional information, like space on disk, other tool incompatibilities etc. OS: Windows
Projects
None yet
Development

No branches or pull requests

3 participants