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

Issue 770229 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: ----



Sign in to add a comment

No justified failure reasons for CQ:16421

Project Member Reported by xixuan@chromium.org, Sep 29 2017

Issue description

https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/16421

There's 3 failures:
guado_moblab-paladin: it's marked as experimental always, so it shouldn't block CQ

wizpig-paladin & reef-paladin: Their HWTest suite are both finished:
http://cautotest-prod.corp.google.com/afe/#tab_id=view_job&object_id=145570669
http://cautotest-prod.corp.google.com/afe/#tab_id=view_job&object_id=145568153
plus they're purple, seems like they're aborted by master.

So what's the real failure for this round of CQ?


 

Comment 1 by nxia@chromium.org, Sep 29 2017

Cc: nxia@chromium.org
Owner: ddavenp...@chromium.org
https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/16421/steps/CommitQueueCompletion/logs/stdio


18:10:10: ERROR: Timeout getting experimental builders from the tree status.


Querying tree status timed out, so CQ didn't know guado_moblab-paladin was marked as experimental. Probably CQ should retry (3 times?) on timeout?

Comment 2 by nxia@chromium.org, Sep 29 2017

http://shortn/_4mIGFaZjTu retry library in chromite.

Comment 3 by xixuan@chromium.org, Sep 29 2017

Labels: -Pri-2 Chase-Pending Pri-1
Status: Started (was: Untriaged)
Labels: -Chase-Pending
Project Member

Comment 6 by bugdroid1@chromium.org, Oct 19 2017

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

commit 4050197f618c635f27fac49d50cd440c44af68e5
Author: Drew Davenport <ddavenport@chromium.org>
Date: Thu Oct 19 02:08:29 2017

cbuildbot: Improve handling of failure fetch tree status

- Allow TimeoutError to propagate out of GetExperimentalBuilders
- If a call to GetExperimentalBuilders times out, don't update
  the list of the experimental builders in the metadata.
- Retry 3 times when fetching tree status

BUG= chromium:770229 
TEST=FEATURES=test emerge chromite

Change-Id: I5cfb56f49d41f775890248db786ea467669383e9
Reviewed-on: https://chromium-review.googlesource.com/695809
Commit-Ready: Drew Davenport <ddavenport@chromium.org>
Tested-by: Drew Davenport <ddavenport@chromium.org>
Reviewed-by: Ningning Xia <nxia@chromium.org>

[modify] https://crrev.com/4050197f618c635f27fac49d50cd440c44af68e5/cbuildbot/validation_pool.py
[modify] https://crrev.com/4050197f618c635f27fac49d50cd440c44af68e5/lib/tree_status_unittest.py
[modify] https://crrev.com/4050197f618c635f27fac49d50cd440c44af68e5/cbuildbot/build_status.py
[modify] https://crrev.com/4050197f618c635f27fac49d50cd440c44af68e5/lib/tree_status.py

Status: Fixed (was: Started)

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

Status: Archived (was: Fixed)

Comment 9 by dchan@chromium.org, Jan 23 2018

Status: Fixed (was: Archived)

Sign in to add a comment