New issue
Advanced search Search tips
Starred by 1 user

Issue metadata

Status: Fixed
Closed: Nov 8
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Task

issue 803111

Sign in to add a comment

Issue 790503: Migrate "wpt-importer" to LUCI

Reported by, Nov 30 2017 Project Member

Issue description

Migrate builder chromium.infra.cron:wpt-importer to LUCI.


Migration app will be posting updates on changes of the migration status.
For the latest status, see

Migration app will close this bug when the builder is entirely migrated from Buildbot to LUCI.

Comment 1 by, Jan 17 2018

Blocking: 803111
Components: Blink>Infra>Ecosystem

Comment 2 by, Jan 18 2018

Labels: -Restrict-View-Google

Comment 3 by, Jan 30 2018

Labels: LUCI-Blocker-P1Builders

Comment 4 by, Feb 13 2018

Labels: -LUCI-Blocker-P1Builders LUCI-Chromium

Comment 5 by, Feb 21 2018

Labels: Pri-2

Comment 6 by, Apr 23 2018

Comment 7 by, Apr 30 2018

This would most likely be migrated together with wpt-exporter ( bug 790570 ).

First step for both of these is to modify the recipe to check the api.runtime.is_experimental recipe attribute, and if the builder is experimental, just do a dry run. Then we'll add the LUCI builder, check that it runs as expected with dry runs and then flip "LUCI is prod". This will make it easy to roll back if something unexpected happens.

Comment 8 by, May 19 2018

Labels: -Pri-2 Pri-3

Comment 9 by, Jul 10 2018

Status: Assigned (was: Available)

Comment 10 by, Jul 10 2018

Description: Show this description

Comment 11 by, Jul 10 2018

Labels: LUCI-Chromium-Mass

Comment 12 by, Jul 10 2018

Labels: Pri-1

Comment 13 by, Sep 8

Labels: LUCI-Mirror-Red

Comment 14 by, Oct 1

Status: Started (was: Assigned)

Comment 15 by, Oct 4

Project Member
Labels: merge-merged-config
The following revision refers to this bug:

commit 2f1e7a9d203304f6e14570ff17fc332d62649800
Author: Nodir Turakulov <>
Date: Thu Oct 04 22:26:17 2018

luci.infra.cron: connect to migration app

Connect luci.infra.cron to migration app because not all builders were migrated
to LUCI yet.

Bug:  790503 
Change-Id: I0ae2a67d17f50955ee869d3540f80dabae20454b
Reviewed-by: Andrii Shyshkalov <>
Commit-Queue: Nodir Turakulov <>


Comment 16 by, Oct 12

Project Member
The following revision refers to this bug:

commit 167121ea09987452572723a78b2d8987b770b751
Author: Robert Ma <>
Date: Fri Oct 12 13:49:45 2018

[WPT import] Add a flag to upload but not submit CL

We used to have only one flag, --auto-update, which controls both
uploading and landing the import CL. This makes testing new setup of the
bot (i.e. LUCI in this case) hard.

This change adds one more flag, --auto-upload, to exercise more steps
(namely uploading and rebaselining), which will be used on the
experimental LUCI builder.

Bug:  790503 
Change-Id: I4ce07fc9ddf15a34c9cb25ba4723d250cad26977
Commit-Queue: Robert Ma <>
Reviewed-by: Quinten Yearsley <>
Cr-Commit-Position: refs/heads/master@{#599197}

Comment 17 by, Oct 12

Project Member
The following revision refers to this bug:

commit ec5a8d649238fad935a09d6ae1f260bde7171b6b
Author: Robert Ma <>
Date: Fri Oct 12 13:51:45 2018

[WPT import] Add --auto-upload to importer on LUCI

To test two more critical steps in the importer: uploading CL and
rebaselining. The flag is being added in .

Bug:  790503 
Change-Id: Id3abeafe573e876019da0c5e06236728053a1168
Reviewed-by: Quinten Yearsley <>
Commit-Queue: Robert Ma <>
Cr-Commit-Position: refs/heads/master@{#18280}

Comment 18 by, Oct 30

Build looks to be working as intended and matches Buildbot results. Can the LUCI builder be flipped to prod?

Comment 19 by, Oct 30

Hi Eric, sorry I was travelling in the last two weeks. Yes, could you please flip the switch to set LUCI as prod? Thanks!

Comment 20 by, Oct 31

Project Member
The following revision refers to this bug:

commit 72b85dbf39aee46060072351c2057bd18913356e
Author: Robert Ma <>
Date: Wed Oct 31 19:51:15 2018

[WPT Import] Stop creating CLs on experimental bot

The experimental builds on LUCI have proven to work as intended and we
are flipping prod to LUCI, so we don't need to create CLs from the
experimental bot anymore. This will save some unnecessary try jobs and
reduce the wait time of *-blink-rel bots.

Bug:  790503 
Change-Id: I7e983165a4df3c327278df0ec77618ce96a7ca45
Auto-Submit: Robert Ma <>
Commit-Queue: Ryan Tseng <>
Reviewed-by: Ryan Tseng <>
Cr-Commit-Position: refs/heads/master@{#18702}

Comment 21 by, Nov 1

Imports are currently failing on chromium_presubmit due to the account being used. See e.g. and

** Presubmit ERRORS ** is not in AUTHORS file. If you are a new contributor, please visit and read the "Legal" section
If you are a chromite, verify the contributor signed the CLA.

Comment 22 by, Nov 2

The issue above seems to have been fixed, but the new account seems to be having trouble with Monorail. From

2018-11-01 22:18:25,607 - URL being requested: GET
2018-11-01 22:18:25,743 - URL being requested: POST
2018-11-01 22:18:25,743 - Attempting refresh to obtain initial access_token
2018-11-01 22:18:25,799 - Refreshing due to a 401 (attempt 1/2)
2018-11-01 22:18:25,827 - Refreshing due to a 401 (attempt 2/2)
Traceback (most recent call last):
  File "/b/swarming/w/ir/kitchen-workdir/src/third_party/blink/tools/", line 26, in <module>
  File "/b/swarming/w/ir/kitchen-workdir/src/third_party/blink/tools/", line 19, in main
  File "/b/swarming/w/ir/kitchen-workdir/src/third_party/blink/tools/blinkpy/w3c/", line 186, in main
    if not self.send_notifications(local_wpt, options.auto_file_bugs, options.monorail_auth_json):
  File "/b/swarming/w/ir/kitchen-workdir/src/third_party/blink/tools/blinkpy/w3c/", line 667, in send_notifications
    dry_run=not auto_file_bugs, service_account_key_json=monorail_auth_json)
  File "/b/swarming/w/ir/kitchen-workdir/src/third_party/blink/tools/blinkpy/w3c/", line 73, in main
    self.file_bugs(bugs, dry_run, service_account_key_json)
  File "/b/swarming/w/ir/kitchen-workdir/src/third_party/blink/tools/blinkpy/w3c/", line 264, in file_bugs
    response = api.insert_issue(bug)
  File "/b/swarming/w/ir/kitchen-workdir/src/third_party/blink/tools/blinkpy/w3c/", line 137, in insert_issue
    return self.api.issues().insert(projectId=issue.project_id, body=body).execute()
  File "/b/swarming/w/ir/cache/vpython/ae31aa/lib/python2.7/site-packages/oauth2client/", line 133, in positional_wrapper
    return wrapped(*args, **kwargs)
  File "/b/swarming/w/ir/cache/vpython/ae31aa/lib/python2.7/site-packages/googleapiclient/", line 840, in execute
    raise HttpError(resp, content, uri=self.uri)
googleapiclient.errors.HttpError: <HttpError 401 when requesting returned "Auth error: Neither client ID '116719108335393041424' nor email '' is whitelisted">
step returned non-zero exit code: 1

Comment 23 by, Nov 6

Project Member
The following revision refers to this bug:

commit d86841e2fe2b3eda485a350a7ef44a489f15009e
Author: Robert Ma <>
Date: Tue Nov 06 18:20:38 2018

[Import Notifier] Get Monorail OAuth token from luci-auth

The application default credential belongs to the default Swarming bot
account, not the dedicated service account for wpt-importer. As
suggested by LUCI task force, we need to use `luci-auth token` instead.

Bug:  790503 
Change-Id: I3257db9a49196fd427c6f2371d00dcabab7ee3a6
Commit-Queue: Robert Ma <>
Reviewed-by: Quinten Yearsley <>
Cr-Commit-Position: refs/heads/master@{#605746}

Comment 24 by, Nov 8

Status: Fixed (was: Started)

Comment 25 by, Dec 17

Project Member
Description: Show this description

Sign in to add a comment