Skip to content

Intermittent errors unpacking Node v18.18.2 #139

@ringods

Description

@ringods

Since I bumped the version of Node to v18.18.2 on a number of my projects in package.json, setting up of this version as part of my github actions workflow frequently fails:

Volta error: Could not unpack Node v18.18.2

Please ensure the correct version is specified.
Volta error: Error cause: failed to unpack `/opt/hostedtoolcache/volta/1.1.1/x64/tmp/.tmp1h3dUo/node-v18.18.2-linux-x64/bin/node`

Error cause: failed to unpack `/opt/hostedtoolcache/volta/1.1.1/x64/tmp/.tmp1h3dUo/node-v18.18.2-linux-x64/bin/node`

Error cause: failed to unpack `node-v18.18.2-linux-x64/bin/node` into `/opt/hostedtoolcache/volta/1.1.1/x64/tmp/.tmp1h3dUo/node-v18.18.2-linux-x64/bin/node`

Error cause: Resource temporarily unavailable (os error 11)

Failing run: https://github.com/pulumiverse/infra/actions/runs/6574407526/job/17859391875

When I trigger the Rerun failed jobs button on the Github web UI, the re-run usually succeeds. For example, here is the re-run which succeeds: https://github.com/pulumiverse/infra/actions/runs/6574407526/job/17862002636

My workflow file: https://github.com/pulumiverse/infra/blob/main/.github/workflows/pull-request.yml#L13-L14

Such intermittent errors don't contribute to a stable CI experience.

Is there any way I can root-cause this error? Has anyone encountered this error also?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions