Closed
Description
Description:
A clear and concise description of what the bug is.
Action version:
'actions/setup-node@v3' (SHA:64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c)
Platform:
- UbuntumacOSWindowsLinux
Runner type:
- HostedSelf-hosted
Tools version:
node: v14.21.3
npm: 6.14.18
yarn: 1.19.1
Repro steps:
Intermittently, the setup-node action times out after 60 minutes. Logs indicate that it's restoring yarn cache.
Expected behavior:
EITHER
- restore cache succeeds quickly
OR - setup-node times out after a minute or two, proceeds without cache
Actual behavior:
- restore cache stalls, and the workflow eventually times out
Activity
bennettp123 commentedon Mar 30, 2023
I initially suspected actions/setup-node needed updating to enable the segment timeout added in actions/cache@v3.0.8.
Upon closer inspection, actions/setup-node uses a version of actions/cache with a default timeout of 60 minutes, not 10 minutes.
As a workaround, I've set a much shorter timeout; I'll report back here if I encounter any further problems 😛
MaksimZhukov commentedon Mar 30, 2023
Hello @bennettp123!
Thank you for reporting this! We will investigate the issue
statico commentedon Apr 18, 2023
We're also experiencing this issue. Disabling the yarn cache fixed our builds temporarily but we'll try this.
millsp commentedon Apr 19, 2023
Same here, we encounter this frequently https://github.com/prisma/prisma/actions/runs/4746282641/jobs/8429723075#step:9:438
millsp commentedon Apr 19, 2023
Related #726
with: node-version
option #788mahabaleshwars commentedon Nov 22, 2024
Hello @bennettp123,
The default timeout has been reduced to 10 minutes. Could you please verify on your end if this resolves the issue? If not, kindly provide the reproduction steps. For reference, you can review the changes made in the options.ts file
mahabaleshwars commentedon Dec 4, 2024
Hello @bennettp123,
Just a quick reminder to check if the issue has been resolved. Please let me know if there's anything else I can assist with!
mahabaleshwars commentedon Dec 11, 2024
Hello @bennettp123, We will be closing this issue for the time being due to lack of recent communication. However, please don't hesitate to reach out if you have any further questions or concerns, and we’ll be happy to reopen the issue as needed.