Yarn frozen-lockfile times out

Build Environment
1

We’ve had a pipeline running for several years, with a job that executes

yarn --frozen-lockfile  --cache-folder ~/.cache/yarn

Yesterday, with no changes, this command suddenly started hanging, and then timing out after 10 minutes. Adding the --verbose flag tell me precisely nothing. Every change I’ve made to the config (bigger docker instance, clean cache etc) makes absolutely no difference.

The command completes normally when executed on a laptop.

Has anyone encountered this issue before? At the moment, we’re pretty much at a loss to work out what the problem is.

1 Like
2

I think I have the same issue but with pnpm. It just hangs:

pnpm install
Lockfile is up to date, resolution step is skipped
Progress: resolved 1, reused 0, downloaded 0, added 0
Packages: +2122

Progress: resolved 2122, reused 0, downloaded 0, added 0
Progress: resolved 2122, reused 1, downloaded 364, added 344
Progress: resolved 2122, reused 1, downloaded 943, added 937
Progress: resolved 2122, reused 1, downloaded 1578, added 1575
Progress: resolved 2122, reused 1, downloaded 2113, added 2112
Progress: resolved 2122, reused 1, downloaded 2117, added 2121
Progress: resolved 2122, reused 1, downloaded 2117, added 2122, done
.../core-js@2.6.12/node_modules/core-js postinstall$ node -e "try{require('./postinstall')}catch(e){}"
.../node_modules/puppeteer postinstall$ node install.js
.../node_modules/@percy/core postinstall$ node ./post-install
.../core-js@2.6.12/node_modules/core-js postinstall: Done
.../node_modules/@percy/core postinstall: Done
.../node_modules/puppeteer postinstall: Chrome (116.0.5845.96) downloaded to /home/circleci/.cache/puppeteer/chrome/linux-116.0.5845.96

Works properly locally. I also SSHed to the container and ran pnpm install from there (--frozen-lockfile on CI by default) and it works :thinking:

Anyone from the CircleCI team that can take a look into this? It looks like the “installing dependencies” step doesn’t see the task ended.

3

It might be connected to puppeteer and its postinstall script. I removed the dependency and the “install dependencies” step doesn’t hang anymore :man_shrugging:

4

same here any updates on this

5

Our CI jobs which have been running fine for months / years and until late last week had npm ci step that took <1 minute now have npm ci take 12 minutes.

In our local dev environments, npm ci still takes <1 minute.

6

puppeteer ends up as the culprit for us as well. I added

PUPPETEER_DOWNLOAD_BASE_URL: "https://storage.googleapis.com/chrome-for-testing-public"

to the environment for our install steps, as suggested on [Bug]: yarn postinstall hangs after browser download · Issue #12833 · puppeteer/puppeteer · GitHub, and it’s back to its regular runtime.

1 Like