No justified failure reasons for CQ:16421 |
|||||||
Issue descriptionhttps://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?
,
Sep 29 2017
http://shortn/_4mIGFaZjTu retry library in chromite.
,
Sep 29 2017
,
Oct 2 2017
,
Oct 2 2017
,
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
,
Oct 19 2017
,
Jan 22 2018
,
Jan 23 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by nxia@chromium.org
, Sep 29 2017Owner: ddavenp...@chromium.org