chromeos-firmware-coral build issues |
|||||
Issue descriptionWhen building the chromeos-firmware-coral package from ToT I get the following error: Started chromeos-base/chromeos-firmware-coral-0.0.1-r68 (logged in /tmp/chromeos-firmware-coral-0.0.1-r68-_Ei0sK) === Start output for job chromeos-firmware-coral-0.0.1-r68 (0m0.3s) === chromeos-firmware-coral-0.0.1-r68: >>> Emerging (1 of 1) chromeos-base/chromeos-firmware-coral-0.0.1-r68::coral-private for /build/coral/ chromeos-firmware-coral-0.0.1-r68: !!! Fetched file: Coral.10068.21.0.tbz2 VERIFY FAILED! chromeos-firmware-coral-0.0.1-r68: !!! Reason: Insufficient data for checksum verification chromeos-firmware-coral-0.0.1-r68: !!! Got: chromeos-firmware-coral-0.0.1-r68: !!! Expected: MD5 RMD160 SHA1 SHA256 SHA512 WHIRLPOOL chromeos-firmware-coral-0.0.1-r68: * Fetch failed for 'chromeos-base/chromeos-firmware-coral-0.0.1-r68', Log file: chromeos-firmware-coral-0.0.1-r68: * '/build/coral/tmp/portage/logs/chromeos-base:chromeos-firmware-coral-0.0.1-r68:20171207-001816.log' chromeos-firmware-coral-0.0.1-r68: >>> Failed to emerge chromeos-base/chromeos-firmware-coral-0.0.1-r68 for /build/coral/, Log file: chromeos-firmware-coral-0.0.1-r68: >>> '/build/coral/tmp/portage/logs/chromeos-base:chromeos-firmware-coral-0.0.1-r68:20171207-001816.log' chromeos-firmware-coral-0.0.1-r68: chromeos-firmware-coral-0.0.1-r68: * Messages for package chromeos-base/chromeos-firmware-coral-0.0.1-r68 merged to /build/coral/: chromeos-firmware-coral-0.0.1-r68: chromeos-firmware-coral-0.0.1-r68: * Fetch failed for 'chromeos-base/chromeos-firmware-coral-0.0.1-r68', Log file: chromeos-firmware-coral-0.0.1-r68: * '/build/coral/tmp/portage/logs/chromeos-base:chromeos-firmware-coral-0.0.1-r68:20171207-001816.log' === Complete: job chromeos-firmware-coral-0.0.1-r68 (0m0.3s) === Failed chromeos-base/chromeos-firmware-coral-0.0.1-r68 (in 0m0.3s). Your build has failed. cros_workon does not seem to alleviate this issue.
,
Dec 7 2017
Quanta broke ToT with this commit: https://chrome-internal.git.corp.google.com/chromeos/overlays/overlay-coral-private/+/d333400be998addf3098c5e64f4dec9bd4863e87%5E%21/#F1 This is the BCS URL problem again. The ebuild had to be updated with some kind of change at the same time to have chromeos-firmware-coral reflect the new BCS URL. The only way to fix it now is to check in such a change.
,
Dec 7 2017
Sheriff here. Sounds like either the manifest file was wrong checksum, or the file uploaded to BCS has been changed or incomplete. No matter what, I think someone should double check what's the right file to be uploaded, or re-upload to BCS. As a result, I'm going to revert the change if no one is already fixing it.
,
Dec 7 2017
Fix at https://chrome-internal-review.googlesource.com/c/chromeos/overlays/overlay-coral-private/+/523459
,
Dec 7 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/overlay-coral-private/+/fbe6ad134a33ec0aa7dc68b6387e8ec63b370aa1 commit fbe6ad134a33ec0aa7dc68b6387e8ec63b370aa1 Author: Jason D. Clinton <jclinton@chromium.org> Date: Thu Dec 07 03:31:30 2017
,
Dec 7 2017
,
Dec 8 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/overlay-coral-private/+/c8e882ba4f424422deddb4056e617a2baeb8360a commit c8e882ba4f424422deddb4056e617a2baeb8360a Author: Jason D. Clinton <jclinton@chromium.org> Date: Fri Dec 08 17:52:16 2017
,
Dec 13 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/overlay-coral-private/+/d9a103eac5d5736353634b20fc50537b9e306e7d commit d9a103eac5d5736353634b20fc50537b9e306e7d Author: Jason D. Clinton <jclinton@chromium.org> Date: Wed Dec 13 22:43:32 2017 |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by adurbin@chromium.org
, Dec 7 2017