New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 615400 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: May 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Beaglebone_servo canary is failing

Reported by jrbarnette@chromium.org, May 27 2016

Issue description

The beaglebone_servo canary builder is consistently failing
the BuildPackages stage:
    https://uberchromegw.corp.google.com/i/chromeos/builders/beaglebone_servo-release/builds/52
    https://uberchromegw.corp.google.com/i/chromeos/builders/beaglebone_servo-release/builds/51
    https://uberchromegw.corp.google.com/i/chromeos/builders/beaglebone_servo-release/builds/50
    https://uberchromegw.corp.google.com/i/chromeos/builders/beaglebone_servo-release/builds/49

The failure itself is inscrutable:
chromeos-bsp-beaglebone_servo-1-r8:  * ERROR: chromeos-base/chromeos-bsp-beaglebone_servo-1-r8::beaglebone_servo failed (install phase):
chromeos-bsp-beaglebone_servo-1-r8:  *   The source directory '/build/beaglebone_servo/tmp/portage/chromeos-base/chromeos-bsp-beaglebone_servo-1-r8/work/chromeos-bsp-beaglebone_servo-1' doesn't exist

However, The problem started at the same time as the arrival
of this CL (which touched the ebuild in question):
    https://chromium-review.googlesource.com/#/c/347027/

 
Owner: jrbarnette@chromium.org
Status: Started (was: Available)
Tackling the revert, on account of I'm sheriff today.  :-/
I've reproduced the problem locally, and seen that the revert
fixes the problem.

Project Member

Comment 3 by bugdroid1@chromium.org, May 27 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/8f2d64547e82577a65400450c38831c2d9f7c332

commit 8f2d64547e82577a65400450c38831c2d9f7c332
Author: Richard Barnette <jrbarnette@chromium.org>
Date: Fri May 27 14:48:47 2016

Revert "Give beaglebone_servo builds an appid"

This reverts commit ba13129a037183a4b8e79a37fffd62da085fc873.

The beaglebone canary started failing when this landed, and
I don't believe in _that_ coincidence.

BUG=chromium:613692, chromium:615400 
TEST=build_packages --board=beaglebone_servo

Change-Id: Ifafb8fb6befb487e33c049baca19f6e81018b2c2
Reviewed-on: https://chromium-review.googlesource.com/347466
Commit-Queue: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@google.com>

[rename] https://crrev.com/8f2d64547e82577a65400450c38831c2d9f7c332/overlay-variant-beaglebone-servo/chromeos-base/chromeos-bsp-beaglebone_servo/chromeos-bsp-beaglebone_servo-1-r9.ebuild
[modify] https://crrev.com/8f2d64547e82577a65400450c38831c2d9f7c332/overlay-variant-beaglebone-servo/chromeos-base/chromeos-bsp-beaglebone_servo/chromeos-bsp-beaglebone_servo-1.ebuild

Though having reverted this may fix the immediate build, it will break other dependencies we have since landed (e.g. signer tests should now fail). 

The build failure should be fixed by https://chromium-review.googlesource.com/#/c/347476/ and we can land the appid again with https://chromium-review.googlesource.com/#/c/347477/ .
> Though having reverted this may fix the immediate build,
> it will break other dependencies we have since landed
> (e.g. signer tests should now fail). 

Signer tests were already failing separately, and that change
got reverted, too.

If you've got a fix that builds, feel free move them forward.



Status: Verified (was: Started)

Sign in to add a comment