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

Issue 804616 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

cq retries slaves after binhost test, adding significant retry delay

Project Member Reported by akes...@chromium.org, Jan 23 2018

Issue description

Example master: https://luci-milo.appspot.com/buildbot/chromeos/master-paladin/17552

Example slave that failed early (in cqsync, due to gerrit flake) the first time: https://luci-milo.appspot.com/buildbot/chromeos/beaglebone-paladin/15892

And then was retried in:
https://luci-milo.appspot.com/buildbot/chromeos/beaglebone-paladin/15893


However, the retry took 50 minutes to occur, becasue the master doesn't kick off the retry until after BinhostTest.


This potentially slows down the CQ significantly; could we run CQCompletion in parallel with binhost test, or some other way to get the retries to happen faster?
 

Comment 1 by nxia@chromium.org, Jan 23 2018

The result of BinhostTest affects the CLs to commit. as we've already separated the logic of committing CLs in CommitQueueHandleChanges, this will be easier to achieve than before.  

Comment 2 by nxia@chromium.org, May 18 2018

Status: WontFix (was: Assigned)
Have improved the performance of BinhostTestStage (reduce the duration from ~30mins to less than 5 mins). this isn't a big problem anymore.

Comment 3 by nxia@chromium.org, May 18 2018

Components: -Infra>Client>ChromeOS Infra>Client>ChromeOS>CI

Sign in to add a comment