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.

Sign up for GitHub

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

Jump to bottom

Intermittent timeouts in actions/setup-node@v3 #733

Open
2 of 6 tasks
bennettp123 opened this issue Mar 30, 2023 · 5 comments · May be fixed by #908
Open
2 of 6 tasks

Intermittent timeouts in actions/setup-node@v3 #733

bennettp123 opened this issue Mar 30, 2023 · 5 comments · May be fixed by #908
Assignees
@dsame
Labels
bug Something isn't working

Comments

@bennettp123
Copy link

Description:
A clear and concise description of what the bug is.

Action version:
'actions/setup-node@v3' (SHA:64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c)

Platform:

  • Ubuntu
  • macOS
  • Windows
  • Linux

Runner type:

  • Hosted
  • Self-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
@bennettp123 bennettp123 added bug Something isn't working needs triage labels Mar 30, 2023
@bennettp123
Copy link
Author

bennettp123 commented Mar 30, 2023 •
edited
Loading

I initially suspected actions/setup-node needed updating to enable the segment timeout added in actions/[email protected].

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 😛

env:
  # https://github.com/actions/cache/blob/04f198bf0b2a39f7230a4304bf07747a0bddf146/tips-and-workarounds.md#cache-segment-restore-timeout
  # -- note that actions/setup-node@3 [uses actions/[email protected]](https://github.com/actions/setup-node/blob/a4fcaaf314b117a40d694a35ee36461f8ff3c6e6/package-lock.json#L41)
  #    which has a [default timeout of 60 minutes](https://github.com/actions/toolkit/blob/457303960f03375db6f033e214b9f90d79c3fe5c/packages/cache/RELEASES.md#304),
  #    not 10 minutes! Let's reduce it further.
  SEGMENT_DOWNLOAD_TIMEOUT_MINS: 2

@MaksimZhukov
Copy link
Contributor

Hello @bennettp123!
Thank you for reporting this! We will investigate the issue

@statico
Copy link

statico commented Apr 18, 2023

We're also experiencing this issue. Disabling the yarn cache fixed our builds temporarily but we'll try this.

@millsp
Copy link

millsp commented Apr 19, 2023

Same here, we encounter this frequently https://github.com/prisma/prisma/actions/runs/4746282641/jobs/8429723075#step:9:438

@millsp
Copy link

millsp commented Apr 19, 2023

Related #726

@dusan-trickovic dusan-trickovic mentioned this issue May 30, 2023
Draft
2 tasks
@dorsegal dorsegal mentioned this issue Jun 20, 2023
Closed
@dsame dsame self-assigned this Sep 26, 2023
@dsame dsame linked a pull request Nov 28, 2023 that will close this issue
Open
2 tasks
@dsame dsame linked a pull request Nov 28, 2023 that will close this issue
Upgrade @actions/cache #908
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dsame dsame

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Upgrade @actions/cache akv-platform/setup-node
6 participants
@statico @dsame @bennettp123 @millsp @MaksimZhukov and others