All mozilla-central Linux jetpack test runs fail with "tar: This does not look like a tar archive": --2011-03-31 20:09:01-- http://hg.mozilla.org/projects/addon-sdk/archive/tip.tar.bz2 Resolving hg.mozilla.org... 10.2.74.67 Connecting to hg.mozilla.org|10.2.74.67|:80... connected. HTTP request sent, awaiting response... 200 Script output follows Length: 2024424 (1.9M) [application/x-tar] Saving to: `jetpack.tar.bz2' 0% [ ] 0 --.-K/s ... 100%[======================================>] 2,024,424 1.54M/s in 1.2s 2011-03-31 20:09:03 (1.54 MB/s) - `jetpack.tar.bz2' saved [2024424/2024424] FINISHED --2011-03-31 20:09:03-- Downloaded: 1 files, 1.9M in 1.2s (1.54 MB/s) tar: This does not look like a tar archive tar: jetpack.tar.bz2: Not found in archive tar: Exiting with failure status due to previous errors program finished with exit code 2 See for example these four test runs (32bit and 64bit Fedora opt and debug) for one push today: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1301627293.1301627353.21307.gz http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1301626294.1301626349.17171.gz http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1301626513.1301626660.18410.gz http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1301627609.1301627664.22784.gz This appears to be a problem with either the run_jetpack.sh script that expands the archive or the tar tool it uses to expand it. Perhaps the script is not specifying the "j" flag to the tar tool to identify the archive as having been compressed with bzip2? Or perhaps the tar tool on those systems doesn't recognize that flag?
Created attachment 523647 [details] [diff] [review] Add a j Looks like myk is right: http://mxr.mozilla.org/build/source/tools/buildfarm/utils/run_jetpack.sh#15
Attachment #523647 - Flags: review?(aki)
Comment on attachment 523647 [details] [diff] [review] Add a j http://hg.mozilla.org/build/tools/rev/1ad7ea35e0bf
Attachment #523647 - Flags: checked-in+
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.