checkout v3 Can't use 'tar -xzf' extract archive file failure

[EgorShtab]

Can't use 'tar -xzf' extract archive file: /home/runner/work/_actions/_temp_94a24dc8-c053-41d2-b3f0-4ac6631faceb/42b68b53-d0be-49dd-8ed2-cece4e18ffba.tar.gz. return code: 2.

when using checkout v3

updating to v4 fixes problem

[patrick-stephens]

Duplicate of #1448 I think

[pimhakkertgc]

Sure, updating to actions/checkout@v4 fixes it, but many bigger repositories can't just update to v4 for their internal workflows or even for deploying. These things take time to implement.

This can't be the fix.

[relloyd]

Same issue here of course. Because of the way we use this action, I now have hundreds of pipelines broken using v3 and potentially 100s of developers blocked 🤦‍♂️

[jontrulson]

Same issue for me... I have several CI machines that can no longer check out code. I cannot update to v4 without some pain, and certainly not soon.

EDIT: Seems to be working again. I restarted the failed jobs and they appear to be running.

[nickatnight]

Same issue for me... I have several CI machines that can no longer check out code. I cannot update to v4 without some pain, and certainly not soon.

EDIT: Seems to be working again. I restarted the failed jobs and they appear to be running.

Restarting the job worked for me, thanks

[gaby]

Updating to v4 doesnt fix it for me, same error. gofiber/storage#962

Ohhh... we have dozens of CI files, why is v3 not working now? 🤦‍♂️

Restarting jobs using Matrix doesnt help, they are randomly failing with the same error.

Why doesnt checkout retry at least 2-3 times on network failures or whatever this is?

[CalvinWilkinson]

I as well am having this issue. So far, when I just re-run the job, it works. I am updating all of my workflows to v4 anyway though. I am currently updating now. If I have any issues with v4, I will comment here.

[douglascayers]

GitHub Status is reporting a new issue with Actions which may be causing this problem

https://www.githubstatus.com/incidents/tqrmcdmghldw

[cory-miller]

Closing this issue as it was related to the previously linked incident.

For clarity since there is minimal detail in the link, repository based actions (such as actions/checkout) are served through a code caching system which had degraded performance.