setup-node: Downloading from nodejs.org failing
I’m not sure this is the best repo to report the issue, if it’s the wrong place please close this 😃
We’ve been using Github Actions successfully for a few days but starting today all our builds have started to fail at the setup-node step with this error:
4m 57s
##[error]Node run failed with exit code 1
Run actions/setup-node@v1
with:
node-version: 12.x
always-auth: false
/bin/tar xzC /home/runner/work/_temp/83341e1a-c86d-4ddb-9963-ef01607f6e1e -f /home/runner/work/_temp/58fc8365-fe95-474e-ad3c-c5511594abdd
gzip: stdin: unexpected end of file
/bin/tar: Unexpected EOF in archive
/bin/tar: Unexpected EOF in archive
/bin/tar: Error is not recoverable: exiting now
##[error]The process '/bin/tar' failed with exit code 2
##[error]Node run failed with exit code 1
Attaching a screenshot for more clarity
You can see an example of a failed build here https://github.com/HabitRPG/habitica/pull/11474/checks?check_run_id=271716057.
The code of the workflow is the standard one that can be seen in the official docs
steps:
.....
- name: Use Node.js ${{ matrix.node-version }}
uses: actions/setup-node@v1
with:
node-version: ${{ matrix.node-version }}
....
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 57
- Comments: 39 (5 by maintainers)
Commits related to this issue
- test: update actions/checkout v2. change step timing. (https://github.com/actions/setup-node/issues/77) — committed to cryptogarageinc/libwally-core by k-matsuzawa 4 years ago
- test: update actions/checkout v2. change step timing. (https://github.com/actions/setup-node/issues/77) — committed to cryptogarageinc/libwally-core by k-matsuzawa 4 years ago
- test: update actions/checkout v2. change step timing. (https://github.com/actions/setup-node/issues/77) — committed to cryptogarageinc/libwally-core by k-matsuzawa 4 years ago
- test: update actions/checkout v2. change step timing. (https://github.com/actions/setup-node/issues/77) — committed to cryptogarageinc/libwally-core by k-matsuzawa 4 years ago
- test: update actions/checkout v2. change step timing. (https://github.com/actions/setup-node/issues/77) — committed to cryptogarageinc/libwally-core by k-matsuzawa 4 years ago
- test: update actions/checkout v2. change step timing. (https://github.com/actions/setup-node/issues/77) — committed to cryptogarageinc/libwally-core by k-matsuzawa 4 years ago
- test: update actions/checkout v2. change step timing. (https://github.com/actions/setup-node/issues/77) — committed to cryptogarageinc/libwally-core by k-matsuzawa 4 years ago
- test: update actions/checkout v2. change step timing. (https://github.com/actions/setup-node/issues/77) — committed to cryptogarageinc/libwally-core by k-matsuzawa 4 years ago
- Merge pull request #77 from akamai/setup-actions Add tests for node 15.x — committed to krzyk/setup-node by akamagorecki 3 years ago
- chore(deps-dev): bump @vercel/ncc from 0.23.0 to 0.24.1 (#77) Bumps [@vercel/ncc](https://github.com/vercel/ncc) from 0.23.0 to 0.24.1. - [Release notes](https://github.com/vercel/ncc/releases) - [... — committed to deining/setup-node by dependabot[bot] 4 years ago
UPDATE:
Yes, it’s external and nodejs downloads (not a CDN) is having. This action just downloads from their endpoint.
https://github.com/nodejs/build/issues/1993
We do have a workitem to cache the latest of each major version on our hosted images and this action checks that cache first (resolved the semver you supply against the cache and if not there queries the cloud).
Downside is you may not get absolute latest (image gen’d yesterday, patch released today). but we have a plan for that as well - an option in the action to always query for cloud first.
You could also fall back on failure the only issue with that takes a long time every invocation when an issue like this is happening and it’s a fresh machine every time.
Thoughts?
Facing this issue today on github actions, with ubuntu-18.04 and node 12.14
test: runs-on: ubuntu-18.04 name: Run unit & integration tests steps: - uses: actions/checkout@v1 - name: Setup Node.js uses: actions/setup-node@v1 with: node-version: 12.14
Same issue on
ubuntu-latestJust ran into this today - would also appreciate a cache service.
I retied couple of times. Waited 10 min, a cup of coffee, tried again and it worked.
I am also having the same issue
Same. The past hour has seen many failures for the Node action. Some jobs it will work, but most don’t.
It’s a download issue. Node is failing to download which causes
taror7zto fail when trying to extract.See this issue: https://github.com/nodejs/build/issues/1993
Possibly related to widespread DNS issues from AWS?
Suddenly completed after rerunning the same action couple of times
Just experimenting right now with Actions, good to know it’s not something I messed up
Hello everyone. We released tag v2 for setup-node. It should resolve some issues related downloading. For details you can take a look on this comment and issue. For now I’m closing the issue. If you have any concerns feel free to ping us.
Same issue.
Running into this today. is anyone still facing this issue?
@bryanmacfarlane I think adding automatic resume to interrupted downloads would be great too. From what I can tell, the file IS being downloaded but it’s so slow it can’t finish before timing out.
as I understand it’s upstream, so…
It’s working for couple of hours already.
I just noticed node published v13 yesterday, might it be related?