chromeos-firmware-reks emerge fails because expected fetched file size is different than actual. |
||||
Issue descriptionreks release has failed build_packages for the last runs because: https://chromegw.corp.google.com/i/chromeos/builders/reks-release/builds/55/steps/BuildPackages%20%5Bafdo_use%5D/logs/stdio === Start output for job chromeos-firmware-reks-0.0.1-r18 (0m9.6s) === chromeos-firmware-reks-0.0.1-r18: >>> Fetching (1 of 1) chromeos-base/chromeos-firmware-reks-0.0.1-r18::reks-private for /build/reks/ chromeos-firmware-reks-0.0.1-r18: 10:27:51: INFO: RunCommand: /mnt/host/source/.cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cp -v -- gs://chromeos-binaries/HOME/bcs-reks-private/overlay-reks-private/chromeos-base/chromeos-firmware-reks/Reks.7287.133.29.tbz2 /var/cache/chromeos-cache/distfiles/target/Reks.7287.133.29.tbz2.tmp chromeos-firmware-reks-0.0.1-r18: !!! Fetched file: Reks.7287.133.29.tbz2 VERIFY FAILED! chromeos-firmware-reks-0.0.1-r18: !!! Reason: Filesize does not match recorded size chromeos-firmware-reks-0.0.1-r18: !!! Got: 2361155 chromeos-firmware-reks-0.0.1-r18: !!! Expected: 2361248 checking the file, it actually is 2361155, so where does 2361248 come from? $ gsutil stat gs://chromeos-binaries/HOME/bcs-reks-private/overlay-reks-private/chromeos-base/chromeos-firmware-reks/Reks.7287.133.29.tbz2 gs://chromeos-binaries/HOME/bcs-reks-private/overlay-reks-private/chromeos-base/chromeos-firmware-reks/Reks.7287.133.29.tbz2: Creation time: Tue, 24 May 2016 00:51:38 GMT Content-Length: 2361155 Content-Type: binary/octet-stream Hash (crc32c): 1NcbiQ== Hash (md5): I4JkqUUM7jkNs8LyclzAzg== ETag: COi+ra2/8cwCEAI= Generation: 1464051098673000 Metageneration: 2
,
May 24 2016
,
May 24 2016
I reverted the original CL. I'm looking into it now.
,
May 24 2016
Thanks Shawn!
,
May 24 2016
My uploads were overwritten by keith: https://www.google.com/chromeos/partner/fe/#bcUpload:type=PRIVATE File contents are the same but compressed file size is different. I'm opening a ticket right now with the cpfe folks to prevent file squashing. |
||||
►
Sign in to add a comment |
||||
Comment 1 by slavamn@chromium.org
, May 24 2016