New issue
Advanced search Search tips

Issue 731429 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Task



Sign in to add a comment

Migrate "linux_chromium_compile_rel_ng" to LUCI

Project Member Reported by luci-mig...@appspot.gserviceaccount.com, Jun 9 2017

Issue description

Migrate builder tryserver.chromium.linux:linux_chromium_compile_rel_ng to LUCI.

Buildbot: https://ci.chromium.org/buildbot/tryserver.chromium.linux/linux_chromium_compile_rel_ng
LUCI: https://ci.chromium.org/buildbucket/luci.chromium.try/linux_chromium_compile_rel_ng

Migration app will be posting updates on changes of the migration status.
For the latest status, see
https://luci-migration.appspot.com/masters/tryserver.chromium.linux/builders/linux_chromium_compile_rel_ng

Migration app will close this bug when the builder is entirely migrated from Buildbot to LUCI.
 
Status: Available (was: Untriaged)

Comment 2 by no...@chromium.org, Jun 9 2017

Labels: -Restrict-View-Google

Comment 3 by efoo@chromium.org, Aug 24 2017

Do not manually mark this bug as "Fixed" when builder is working as intended (WAI) on LUCI. Migration is not complete until builder is solely on LUCI.

The LUCI migration app will mark the bug status to "Fixed" automatically when the BuildBot builder equivalent is turned down. 
Project Member

Comment 4 by luci-mig...@appspot.gserviceaccount.com, Sep 21 2017

Description: Show this description

Comment 5 by no...@chromium.org, Dec 6 2017

Labels: SchedulingType-Try
Owner: martiniss@chromium.org
Status: Started (was: Available)
I'm doing this.

According to https://uberchromegw.corp.google.com/i/tryserver.chromium.linux/buildslaves this bot has 12 buildbot machines assigned to it.
Cc: estaab@chromium.org no...@chromium.org
All 12 of those machines are shared by other bots.

Also, this builder gets incredibly low traffic. Maybe one build a week. So, we should either give it a dedicated machine (probably only one), or have it use a pool? Not sure if that's a standard thing at all. Adding people who might know.
I'm going to just use a single machine. I think we can change this fairly easily later on; this builder doesn't have much traffic.

I'm also going to set the experiment traffic to 100%, since it has such a small amount of traffic.
Project Member

Comment 9 by bugdroid1@chromium.org, Jan 30 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/77239282ac444148c659397ab7793d2dd58ed140

commit 77239282ac444148c659397ab7793d2dd58ed140
Author: Stephen Martinis <martiniss@google.com>
Date: Tue Jan 30 01:53:36 2018

I ran a CL and it passed on buildbot and LUCI. I'm going to wait a week or two, hopefully a few CLs will hit this bot.

Comment 11 by efoo@chromium.org, Jan 30 2018

Labels: LUCI-Blocker-CQSets

Comment 12 by efoo@chromium.org, Feb 13 2018

Labels: -LUCI-Blocker-CQSets LUCI-Chromium-CQSets

Comment 13 by efoo@chromium.org, Mar 7 2018

Labels: Pri-1
Project Member

Comment 14 by bugdroid1@chromium.org, Mar 8 2018

Project Member

Comment 15 by bugdroid1@chromium.org, Mar 13 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/master-manager/+/8bf9106d3950bf78bbcad86c2dd23c3dddeab596

commit 8bf9106d3950bf78bbcad86c2dd23c3dddeab596
Author: Ryan Tseng <hinoka@google.com>
Date: Tue Mar 13 00:24:32 2018

Project Member

Comment 16 by luci-mig...@appspot.gserviceaccount.com, May 10 2018

Labels: MigrationStatus-WAI
Status: Fixed (was: Started)
Status changed to "Migrated"
Labels: LUCI-Chromium-Manual
Description: Show this description

Sign in to add a comment