Skip to content

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

New issue
New issue
Closed
Closed
Intermittent timeouts in actions/setup-node@v3#733
Assignees
mahabaleshwars
Labels
bugSomething isn't working
@bennettp123

Description

@bennettp123
bennettp123
opened on Mar 30, 2023

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

Activity

bennettp123
added
bugSomething isn't working
needs triage
on Mar 30, 2023
bennettp123

bennettp123 commented on Mar 30, 2023

@bennettp123
bennettp123
on Mar 30, 2023 · edited by bennettp123
Author

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 😛

env:
  # https://github.com/actions/cache/blob/04f198bf0b2a39f7230a4304bf07747a0bddf146/tips-and-workarounds.md#cache-segment-restore-timeout
  # -- note that actions/setup-node@3 [uses actions/cache@3.0.4](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

MaksimZhukov commented on Mar 30, 2023

@MaksimZhukov
MaksimZhukov
on Mar 30, 2023
Contributor

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

MaksimZhukov
removed
needs triage
on Mar 30, 2023
statico

statico commented on Apr 18, 2023

@statico
statico
on Apr 18, 2023

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

millsp

millsp commented on Apr 19, 2023

@millsp
millsp
on Apr 19, 2023

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

millsp

millsp commented on Apr 19, 2023

@millsp
millsp
on Apr 19, 2023

Related #726

dusan-trickovic
mentioned this on May 30, 2023
dorsegal
mentioned this on Jun 20, 2023
dsame
self-assigned this
on Sep 26, 2023
dsame
mentioned this on Nov 28, 2023
dsame
linked a pull request that will close this issueUpgrade @actions/cache #908on Nov 28, 2023
mahabaleshwars
assigned
mahabaleshwars
and unassigned
dsame
on Nov 21, 2024

4 remaining items

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    Participants

    @statico@dsame@bennettp123@millsp@MaksimZhukov

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