New issue
Advanced search Search tips

Issue 697620 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

git cl try failing

Project Member Reported by npm@chromium.org, Mar 1 2017

Issue description

(1) I created a CL, landed changes at https://pdfium-review.googlesource.com/2892
(2) I did git cl try on command line for Patchset 3, output was "scheduled CQ Dry Run on https://pdfium-review.googlesource.com/2892"
(3) But instead of doing a dry run, I was added as a reviewer with my @google account, and Chromium bot said: "Dry run: only CL owners or full committers are allowed to trigger CQ dry run"

What is the expected result?
git cl try works just as CQ dry run button

It seems the problem is that git cl try tries to use my @google account for some reason.
 
Cc: aga...@chromium.org
Labels: Pri-2
Owner: tandrii@chromium.org
Status: Assigned (was: Untriaged)
This may be an issue with your .gitcookies.

When you generated your password for pdfium-review, did you use your chromium.org account?
Cc: tandrii@chromium.org
Owner: npm@chromium.org
What Andy 

Specifically, can you ensure that the two lines for pdfium host have the chromium.org account

  pdfium.googlesource.com
  pdfium-review.googlesource.com

and make sure you don't have this line:
  
  *.googlesource.com   foo bar  ldap@google.com

instead expanding it to {$HOST, $HOST-review}.googlesource.com for each $HOST you need.

Please retry "git cl try -v -v" after that. If it still doesn't work, assign back to me and copy-paste whatever last command printed.

Comment 3 by npm@chromium.org, Mar 6 2017

Status: Verified (was: Assigned)
Ok, thanks.

Sign in to add a comment