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

Issue 824913 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 752342



Sign in to add a comment

Move Scheduled PreCQ builds to swarming

Project Member Reported by dgarr...@chromium.org, Mar 22 2018

Issue description

I'm starting the process of moving PreCQ Launcher launched tryjobs to swarming.

To support load, I'm moving 170 of 180 PreCQ builders from the waterfall to swarming. The 10 left behind are for manually launched PreCQ builds, and will move when the chromiumos.tryserver waterfall is shutdown.

The planned process is:
  6 PM: Pause and abort the PreCQ Launcher to drain the waterfall.
  7 PM: Destroy the builders cros-standard{10..181}-c2
          ccompute di cros-standard{10..181}-c2
        Land CL:*593642  (can already be landed in a different local branch)
        Create the builders swarm-cros-{40..209}
          ccompute ai swarm-cros-{40..209}
        Chump CL:974577 (launcher will use --swarming)
        Unpause the launcher.

Note that the builders in question will remain in the tryserver waterfall configuration. That allows us to avoid a waterfall restart, and makes it easier to transition these builders back if that becomes necessary. They will simply appear as "offline".

The revert process if necessary:
  Pause/abort the PreCQ Launcher to drain.
  Revert CL:974577
  Destroy the new swarming builders.
  Revert CL:*593642
  Re-create the waterfall builders.
  Unpause the Pre CQ Launcher


PreCQ Launcher Scheduler link for pause/unpause:
  https://luci-scheduler.appspot.com/jobs/chromiumos-chromite/pre-cq-launcher
 
 
Blocking: 752342
The initial transition is finished. The builders and the precq-launcher have been updated.

Waiting to see how stable it is!
Project Member

Comment 3 by bugdroid1@chromium.org, Mar 23 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/infra_internal/+/b21b8b7f803aa5e813c0354c34d254cd5df279ec

commit b21b8b7f803aa5e813c0354c34d254cd5df279ec
Author: Don Garrett <dgarrett@google.com>
Date: Fri Mar 23 01:59:49 2018

Project Member

Comment 4 by bugdroid1@chromium.org, Mar 23 2018

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

commit ce913b499c4c8828543e0d32179c2f7709705b2b
Author: Don Garrett <dgarrett@google.com>
Date: Fri Mar 23 02:01:56 2018

precq_launcher: Use swarming for PreCQ builds.

Move PreCQ builds from buildbot to swarming. This must be coordinated
with a move of builders to maintain sufficient build capacity.

BUG= chromium:824913 
TEST=run_tests + previous efforts in chromium:823445

Change-Id: I3440d5c3e634134e3278222f5cbd401ac22e8525
Reviewed-on: https://chromium-review.googlesource.com/974577
Reviewed-by: Ningning Xia <nxia@chromium.org>
Tested-by: Don Garrett <dgarrett@chromium.org>

[modify] https://crrev.com/ce913b499c4c8828543e0d32179c2f7709705b2b/cbuildbot/stages/sync_stages.py

Project Member

Comment 5 by bugdroid1@chromium.org, Mar 23 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/e400a31c6784e7977644610679075b2a5571aeb9

commit e400a31c6784e7977644610679075b2a5571aeb9
Author: chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Fri Mar 23 03:23:35 2018

Roll src/third_party/chromite/ 0fba0a0ea..ce913b499 (1 commit)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/0fba0a0ea755..ce913b499c4c

$ git log 0fba0a0ea..ce913b499 --date=short --no-merges --format='%ad %ae %s'
2018-03-21 dgarrett precq_launcher: Use swarming for PreCQ builds.

Created with:
  roll-dep src/third_party/chromite
BUG= chromium:824913 


The AutoRoll server is located here: https://chromite-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=chrome-os-gardeners@chromium.org

Change-Id: I68adb369aa4308bffac9ba41b270527f8dabd9d4
Reviewed-on: https://chromium-review.googlesource.com/977323
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#545359}
[modify] https://crrev.com/e400a31c6784e7977644610679075b2a5571aeb9/DEPS

Status: Fixed (was: Started)
Seems to be working as expected.

Sign in to add a comment