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

Issue 755813 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

reef-uni-paladin buildpackage error

Project Member Reported by nxia@chromium.org, Aug 16 2017

Issue description

This bug is opened to track a bad CL, sheriffs@, can you please help to find the bad CL for this failure ?

https://luci-milo.appspot.com/buildbot/chromeos/reef-uni-paladin/50


 

Comment 1 by nxia@chromium.org, Aug 16 2017

a bad cl candidate:
 https://chromium-review.googlesource.com/c/614310
Cc: sjg@chromium.org jclinton@chromium.org
The CL author claims that there was a BCS flake in fetching the ec blob for pyro.

Looking at the logs for that failing build nothing supports / rejects this hypothesis.

Is all the unibuild development happening on reef-uni? If so, perhaps we need a reef-uni-pre-cq to get build coverage for unibuilds before they hit CQ? Or is there already a pre-cq config with unified builds?

That CL is being tested with the following pre-cq set:
The Pre-Commit Queue has picked up your change. You can follow along at 
(nyan_blaze-no-vmtest-pre-cq) : https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/no_vmtest_pre_cq/98415 
(betty-pre-cq) : https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/pre_cq/50162 
(lumpy-no-vmtest-pre-cq) : https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/no_vmtest_pre_cq/98421 
(samus-no-vmtest-pre-cq) : https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/no_vmtest_pre_cq/98416 
(whirlwind-no-vmtest-pre-cq) : https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/no_vmtest_pre_cq/98418 
(kevin-no-vmtest-pre-cq) : https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/no_vmtest_pre_cq/98417 
(daisy_spring-no-vmtest-pre-cq) : https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/no_vmtest_pre_cq/98414 
(cyan-no-vmtest-pre-cq) : https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/no_vmtest_pre_cq/98419 
(reef-no-vmtest-pre-cq) : https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/no_vmtest_pre_cq/98420 
(binhost-pre-cq) : https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/pre_cq/50163  .

And nothing obviously says it's a unified build. We could convert reef-pre-cq to be reef-uni-pre-cq...
Owner: jclinton@chromium.org
Status: Assigned (was: Untriaged)
What is the pre-cq support for reef-uni at the moment? What do we have to make sure build_package errors are caught before the CQ?
Owner: shapiroc@chromium.org
Project Member

Comment 6 by bugdroid1@chromium.org, Aug 23 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/84ce4ef4ee704d0d7f68a342950360a529705bfd

commit 84ce4ef4ee704d0d7f68a342950360a529705bfd
Author: C Shapiro <shapiroc@chromium.org>
Date: Wed Aug 23 02:05:11 2017

[unibuild] Add reef-uni to the pre-cq test battery

We currently have no unified build coverage pre-cq.
This is is where a lot of work is currently taking place and it needs
the corresponding coverage.

BUG= chromium:755813 
TEST=cbuildbot --remote reef-uni-no-vmtest-pre-cq

Change-Id: I1f535a269d5f741cc2403af0bbb5ac48316b9591
Reviewed-on: https://chromium-review.googlesource.com/621880
Commit-Ready: C Shapiro <shapiroc@google.com>
Tested-by: C Shapiro <shapiroc@google.com>
Reviewed-by: Simon Glass <sjg@chromium.org>

[modify] https://crrev.com/84ce4ef4ee704d0d7f68a342950360a529705bfd/lib/constants.py

Status: Fixed (was: Assigned)

Comment 8 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Sign in to add a comment