New issue
Advanced search Search tips

Issue 731427 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Aug 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Task



Sign in to add a comment

Migrate "win_nacl_sdk" to LUCI

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

Issue description

Migrate builder tryserver.chromium.win:win_nacl_sdk to LUCI.

Buildbot: https://ci.chromium.org/buildbot/tryserver.chromium.win/win_nacl_sdk
LUCI: https://ci.chromium.org/buildbucket/luci.chromium.try/win_nacl_sdk

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.win/builders/win_nacl_sdk

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

Comment 6 by efoo@chromium.org, Feb 21 2018

Labels: LUCI-Chromium Pri-1
Project Member

Comment 7 by bugdroid1@chromium.org, Jun 13 2018

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

commit 801017e14269364a104fbe1fbcddf4049bc87830
Author: Ryan Tseng <hinoka@google.com>
Date: Wed Jun 13 00:47:22 2018

Comment 8 by hinoka@chromium.org, Jun 15 2018

Labels: LUCI-Mirror-Red
This requires nacl_sdk_buildbot_run.py in build.git

Comment 9 by efoo@chromium.org, Jun 19 2018

Cc: dpranke@chromium.org
This builder is mirrored to LUCI but results do not match Buildbot production output. 

CC'ing dpranke to triage to someone to fix. 

For details on how to flip this mirrored LUCI builder to production, see go/migrate2luci under Step 3. 
Labels: LUCI-Chromium-Mass
Cc: hinoka@chromium.org
Owner: dschuff@chromium.org
As per discussion with Dirk, assigning these to Derek to triage. 

Derek, these builders were mirrored to LUCI using the same process as I explained to be used for client.nacl* LUCI migrations. Unfortunately, these builders (<platform>_nacl_sdk) are failing on LUCI for various reasons (annotated steps won't run, unittests fails, missing MSVC).

Can you take a look and assign these to folks to take a look and fix? If you have any questions, please reach out to Ryan who did the mirror to LUCI. 
Derek, have you had the chance to take a look at this and triage? Thanks!
Status: Assigned (was: Available)
Owner: efoo@chromium.org
Confirmed with dschuff@ that this SDK builder can be turned down since they are no longer needed. 

Re-assigned to efoo@
Status: WontFix (was: Assigned)
These masters are being turned down.
Status: Assigned (was: WontFix)
Project Member

Comment 17 by bugdroid1@chromium.org, Aug 20

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

commit 68e92b19a0823468c0d40a335a746d854166408f
Author: Eric Foo <efoo@google.com>
Date: Mon Aug 20 23:51:31 2018

Status: Fixed (was: Assigned)
Deleted in LUCI and Buildbot. Marking fixed
Description: Show this description

Sign in to add a comment