New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.
Starred by 1 user
Status: Archived
Owner:
jclinton@chromium.org
Closed: Dec 2017
Cc:
█ pho...@chromium.org
ren....@quantatw.com
█ pyeh@chromium.org
ejcaruso@chromium.org
jclinton@chromium.org
sjg@chromium.org
shapiroc@chromium.org
adurbin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment
link

Issue 792753: chromeos-firmware-coral build issues

Reported by ejcaruso@chromium.org, Dec 7 2017 Project Member 
When 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.

Comment 1 by adurbin@chromium.org, Dec 7 2017

Cc: sjg@chromium.org shapiroc@chromium.org jclinton@chromium.org

Comment 2 by jclinton@chromium.org, 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.

Comment 3 by hungte@chromium.org, 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.

Comment 4 by jclinton@chromium.org, Dec 7 2017

Cc: ren....@quantatw.com pyeh@chromium.org
Owner: jclinton@chromium.org
Status: Started (was: Available)
Fix at https://chrome-internal-review.googlesource.com/c/chromeos/overlays/overlay-coral-private/+/523459

Comment 5 by bugdroid1@chromium.org, Dec 7 2017

Project Member 
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

Comment 6 by jclinton@chromium.org, Dec 7 2017

Status: Fixed (was: Started)

Comment 7 by bugdroid1@chromium.org, Dec 8 2017

Project Member
Labels: merge-merged-release-R64-10176.B
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

Comment 8 by bugdroid1@chromium.org, Dec 13 2017

Project Member
Labels: merge-merged-factory-coral-10122.B
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

Comment 9 by dchan@google.com, Jul 30 2018

Status: Archived (was: Fixed)
►

Sign in to add a comment