edgar paladin fails consistently - overlay is misconfigured
Reported by
jrbarnette@chromium.org,
Jul 18 2017
|
|||
Issue description
The edgar paladin builder is consistently failing in the
UploadPrebuilts stage.
Here's the relevant error from the most recent run:
11:05:45: ERROR: No Google Storage ACL file googlestorage_acl.txt found in edgar overlay.
I am reliably informed that this means the overlay was created
with an incorrect configuration.
Marking P1 - A red paladin seems like a Bad Thing (TM) even when
experimental, so I'd like to see this cleaned up on some reasonable
time frame.
,
Jul 18 2017
https://chrome-internal-review.googlesource.com/#/c/413498/ should fix it, it is surprising this went so long unnoticed even independent of the paladin. The fall out here is just that partners never got proper pre-builts, which apparently did not get used much for this project.
,
Jul 18 2017
> [ ... ] it is surprising this went so long unnoticed even independent of the paladin. I think that, independent of the paladin, there was very little to notice. If there were no downstream consumers for the pre-builts, then there was no one to care, until the paladin tried to become non-experimental.
,
Jul 18 2017
And downstream consumers will work correctly, just slowly.
,
Jul 19 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/overlay-edgar-private/+/4280a87fc1cb89af3de483388750ca66702d6619 commit 4280a87fc1cb89af3de483388750ca66702d6619 Author: Bernie Thompson <bhthompson@google.com> Date: Wed Jul 19 02:39:06 2017
,
Aug 7 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by jrbarnette@chromium.org
, Jul 18 2017Status: Assigned (was: Unconfirmed)