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

Issue 839635 link

Starred by 1 user

Issue metadata

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

Blocking:
issue 838970



Sign in to add a comment

Trigger error on GPU FYI Win Builder

Project Member Reported by cwallez@chromium.org, May 3 2018

Issue description

Since this build, https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/GPU%20FYI%20Win%20Builder/4342 GPU FYI Win Builder fails the trigger step.

Looking at the log file we can see an RPC error:
RPC failed permanently: rpc error: code = NotFound desc = no such job or no READ permission: chromium/Win10 FYI Exp Release (Intel HD 630) {"error":"rpc error: code = NotFound desc = no such job or no READ permission: chromium/Win10 FYI Exp Release (Intel HD 630)", "host":"luci-scheduler.appspot.com", "method":"EmitTriggers", "service":"scheduler.Scheduler"}
rpc error: code = NotFound desc = no such job or no READ permission: chromium/Win10 FYI Exp Release (Intel HD 630)
step returned non-zero exit code: 5

This seems to be caused by https://chromium-review.googlesource.com/c/chromium/tools/build/+/1041145 that adds the builder referenced in the error.

zmo, can you TAL? The trigger failure makes a bunch of configurations not run any tests at all right now.
 

Comment 1 by kbr@chromium.org, May 4 2018

Blocking: 838970
Status: Fixed (was: Available)
Sorry I didn't notice this as pixel wrangler. I should have been monitoring the waterfall more closely. For the record, the revert went in as https://chromium-review.googlesource.com/1043365 and this will / should fix this trigger error.

Will comment on the parent bug regarding the order the CLs need to land in.

Sign in to add a comment