New issue
Advanced search Search tips

Issue 864087 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Task

Blocked on:
issue 868204



Sign in to add a comment

Migrate "nacl-presubmit" to LUCI

Project Member Reported by luci-mig...@appspot.gserviceaccount.com, Jul 16

Issue description

Migrate builder tryserver.nacl:nacl-presubmit to LUCI.

Buildbot: https://ci.chromium.org/buildbot/tryserver.nacl/nacl-presubmit
LUCI: https://ci.chromium.org/buildbucket/luci.nacl.try/nacl-presubmit

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

Migration app will close this bug when the builder is entirely migrated from Buildbot to LUCI.
 
Labels: LUCI-Clients-Mass LUCI-Mig-Client LUCI-Clients
Blockedon: 868204
Labels: -Restrict-View-Google
Builders are blocked on master bug 868204
Builders are mirrored (https://ci.chromium.org/p/nacl/g/try/builders) but mostly are red or purple. 

Pending hinoka@ to review and hand off to dschuff@. Updates to follow. 
Labels: -Pri-3 Pri-1
Owner: hinoka@chromium.org
Status: Assigned (was: Available)
Builder is oddly failing in annotated steps due to the following error: 

ERROR - unset/invalid builder name

Assigned to hinoka@ to take a look to see if this is an mirror config issue. 

Comment 5 Deleted

Owner: hinoka@chromium.org
The error message has changed but it still seems to be in infra code: https://ci.chromium.org/p/nacl/builders/luci.nacl.try/nacl-presubmit/8
Cc: dschuff@chromium.org
Cc: efoo@chromium.org
Builder flipped to LUCI. Assigned to Derek to fix issues and close. 
Owner: dschuff@chromium.org
There's still an exception in the general recipe infrastructure code (not even in the nacl-specific recipe): https://ci.chromium.org/p/nacl/builders/luci.nacl.try/nacl-presubmit/1063 , specifically https://logs.chromium.org/logs/nacl/buildbucket/cr-buildbucket.appspot.com/8927207766875636512/+/steps/Uncaught_Exception/0/logs/exception/0

Do I need to add something to scripts/slave/recipes/nacl.py to inject that property into api.properties? 
Also (and I'm not sure there's a bug filed for this?) but what do we need to do to make 'git cl' launch LUCI try jobs? It's still only ever launching buildbot jobs, which are now all purple.
Just realized the the CQ actually does seem to be doing the right thing (e.g. for dry run type try jobs). It's just 'git cl try' that I was seeing.
Description: Show this description

Sign in to add a comment