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

Issue 636046 link

Starred by 1 user
Status: Fixed
Owner:
dpranke@chromium.org
Closed: Aug 2016
Cc:
█ phajdan.jr@chromium.org
tandrii@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

The CQ incorrectly failed the CLA check for manojkumar.bhosale@imgtec.com

Project Member Reported by dpranke@chromium.org, Aug 9 2016 
In https://codereview.chromium.org/2150943003/ the CQ rejected the change, claiming
that the patch author hadn't signed the CLA, but they should've been covered under
the corporate CLA for imgtec.

Can someone look into this and figure out what went wrong?

Comment 1 by tandrii@chromium.org, Aug 9 2016

Owner: tandrii@chromium.org
Status: Assigned (was: Untriaged)
Will look.

Comment 2 by tandrii@chromium.org, Aug 9 2016

Owner: dpranke@chromium.org
Nothing interesting in the logs:

[I2016-08-09T12:37:35.971878-07:00 10703 140145346148160 verification.sign_cla:55] SignCLA result for manojkumar.bhosale@imgtec.com: 0

I also verified that checks right before and after this for other users returned 1, so I don't think CQ code is broken.

Thus, I think you should re-assign this to owners of CLA https://cla.developers.google.com service. Assinign back to you for now.

Comment 3 by dpranke@chromium.org, Aug 9 2016 

@tandrii - thanks for taking a look. I'll see if I can follow up w/ the CLA team.

Comment 4 by dpranke@chromium.org, Aug 30 2016

Status: Fixed (was: Assigned)
This was a CLA issue and has been resolved. Closing.

Comment 5 by serg...@chromium.org, Aug 31 2016

Cc: -serg...@chromium.org
►

Sign in to add a comment