kevin-release build failing when building chromeos-firmware-kevin package. |
||||||||
Issue descriptionkevin canary is failing: https://uberchromegw.corp.google.com/i/chromeos/builders/kevin-release/builds/288 === Start output for job chromeos-firmware-kevin-0.0.1-r17 (0m0.2s) === chromeos-firmware-kevin-0.0.1-r17: >>> Emerging (1 of 1) chromeos-base/chromeos-firmware-kevin-0.0.1-r17::kevin-private for /build/kevin/ chromeos-firmware-kevin-0.0.1-r17: * kevin_fw_8676.0.2016_08_05.tbz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] chromeos-firmware-kevin-0.0.1-r17: * kevin_ec_8676.0.2016_08_05.tbz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] chromeos-firmware-kevin-0.0.1-r17: !!! Fetched file: kevin_B2_cr50.4957.tbz2 VERIFY FAILED! chromeos-firmware-kevin-0.0.1-r17: !!! Reason: Insufficient data for checksum verification chromeos-firmware-kevin-0.0.1-r17: !!! Got: chromeos-firmware-kevin-0.0.1-r17: !!! Expected: MD5 RMD160 SHA1 SHA256 SHA512 WHIRLPOOL chromeos-firmware-kevin-0.0.1-r17: * Fetch failed for 'chromeos-base/chromeos-firmware-kevin-0.0.1-r17', Log file: chromeos-firmware-kevin-0.0.1-r17: * '/build/kevin/tmp/portage/logs/chromeos-base:chromeos-firmware-kevin-0.0.1-r17:20160808-113221.log' chromeos-firmware-kevin-0.0.1-r17: >>> Failed to emerge chromeos-base/chromeos-firmware-kevin-0.0.1-r17 for /build/kevin/, Log file: chromeos-firmware-kevin-0.0.1-r17: >>> '/build/kevin/tmp/portage/logs/chromeos-base:chromeos-firmware-kevin-0.0.1-r17:20160808-113221.log' chromeos-firmware-kevin-0.0.1-r17: chromeos-firmware-kevin-0.0.1-r17: * Messages for package chromeos-base/chromeos-firmware-kevin-0.0.1-r17 merged to /build/kevin/: chromeos-firmware-kevin-0.0.1-r17: chromeos-firmware-kevin-0.0.1-r17: * Fetch failed for 'chromeos-base/chromeos-firmware-kevin-0.0.1-r17', Log file: chromeos-firmware-kevin-0.0.1-r17: * '/build/kevin/tmp/portage/logs/chromeos-base:chromeos-firmware-kevin-0.0.1-r17:20160808-113221.log' === Complete: job chromeos-firmware-kevin-0.0.1-r17 (0m0.2s) ===
,
Aug 8 2016
moch@ appears as if you changed the ebuild last? Can you take a look?
,
Aug 8 2016
Vadim, the file that is failing verification (kevin_B2_cr50.4957.tbz2) seems to have been updated by you last. Can you please take a look.
,
Aug 8 2016
Mohamed, the manifest file is not matching the kevin_B2_cr50.4957.tbz2. The manifest was changed when you uploaded https://chrome-internal-review.googlesource.com/273505 You can generate the correct manifest by running ebuild-kevin-tpm2 chromeos-firmware-kevin-9999.ebuild manifest in src/private-overlays/overlay-kevin-private/chromeos-base/chromeos-firmware-kevin manifest generated by this command is different from what you uploaded. I can't try this with ebuild-kevin as I don't have overlay for it any more. I was calling for having a separate firmare-kevin-tpm2 ebuild, but was told that creating a folder on bcs is too much effort.
,
Aug 8 2016
I guess I ran the command "ebuild-kevin chromeos-firmware-kevin-9999.ebuild manifest" This is confusing!
,
Aug 8 2016
Vadim, I ran the command "ebuild-kevin-tpm2 chromeos-firmware-kevin-9999.ebuild manifest" in the kevin private overlay. I still don't see the firmware hash for kevin_B2_cr50.4957.tbz2 included in the Manifest file.
,
Aug 8 2016
https://chrome-internal-review.googlesource.com/#/c/273626/2
,
Aug 29 2016
,
Aug 29 2016
bulk verified
,
Aug 29 2016
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by vbendeb@chromium.org
, Aug 8 2016