Not in gzip format
See original GitHub issueHi, I am getting an error when running the setup-java step in the following configuration:
- uses: actions/setup-java@v1
with:
java-version: '12.x'
The error I get is the following:
Run actions/setup-java@v1
/bin/tar xzC /home/runner/work/_temp/temp_1966052730 -f /home/runner/work/_temp/7c187b07-8201-4bf2-b87d-247013d1c81d
gzip: stdin: not in gzip format
/bin/tar: Child returned status 1
/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
After doing some googling, this looks to be the most relatable problem, but I notice it’s not being downloaded the Oracle site, rather from this site so I don’t think cookies are the issue. Has anyone else also encountered this error?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:27
- Comments:24 (8 by maintainers)
Top Results From Across the Web
How to solve: stdin: not in gzip format - It's FOSS
Reason: Reason for the error is quite evident. The file is not a gzipped file but a POSIX tar archive file. Which means...
Read more >How to solve gzip: stdin: not in gzip format error - Linux Hint
The error “gzip: stdin: not in gzip format” occurs when the file is not in the gzip format. There are two cases; either...
Read more >stdin: not in gzip format tar: Child returned status 1 tar: Error is ...
This means the file isn't really a gzipped tar file -- or any kind of gzipped file -- in spite of being named...
Read more >[SOLVED] gzip: stdin: not in gzip format - LinuxForDevices
In this article, we will discuss how to solve gzip: stdin: not in gzip format error while extracting a zipped file using the...
Read more >How to Solve gzip: stdin: Not in gzip Format Error
Solution for the gzip: stdin: not in gzip format error ... 1. To solve the error, first, we need to check the file...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Looks like some added .sig files (.tar.gz.sig) on the CDN were being confused for the .tar.gz files by installer.ts. The .sig files have been removed from the CDN for now, but are the tool-cache seems to have cached them.
This has started to fail for us again today. Anyone else experiencing it?