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

Issue 605759 link

Starred by 1 user
Status: Fixed
Owner: ----
Closed: Apr 2016
Cc:
akes...@chromium.org
█ davidjames@chromium.org
snanda@chromium.org
d...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

CL won't go through commit-queue, Gerrit says "forbidden" though tree is open

Project Member Reported by kirtika@chromium.org, Apr 21 2016 
Me and snanda@ tried to mark this CL as commit-queue ready: https://chromium-review.googlesource.com/#/c/339675/ and failed. Could you help us commit this? 
We need this for a large merge, one each on kernel versions {3.8 through 4.4}. 

The error on the CL comments is: 
The Pre-Commit Queue failed to submit your change in https://uberchromegw.corp.google.com/i/chromeos/builders/pre-cq-launcher/builds/6803 . CL:339675 could not be submitted by the CQ. The error message from Gerrit was: Forbidden

Comment 1 by akes...@chromium.org, Apr 22 2016 

Looks to me like your CL wasn't marked as Verified(+1) when this message was posted, or you were right in the midst of applying it when the message was posted.

Comment 2 by akes...@chromium.org, Apr 22 2016 

Hmm, never mind, you already retried...

Comment 3 by akes...@chromium.org, Apr 22 2016 

Oh, this is a config CL. The CQ doesn't usually apply those. In fact, I didn't even think it picked them up.

Just click Submit directly on the CL. Or I can do so, if you don't have permissions.

Comment 4 by d...@chromium.org, Apr 22 2016

Status: Fixed (was: Untriaged)
Oh thanks for pointing that out, akeshet@, I hadn't noticed that. Okay, makes sense since the bot isn't an owner of the repository, so it can't push change updates.

I went ahead and submitted.
►

Sign in to add a comment