w3c-test-autoroller email address doesn't match user account |
|||||
Issue description# err> error: failed to push some refs to 'https://chromium.googlesource.com/a/chromium/src' # err> ERROR:git-retry:Process failure was not known to be transient; terminating with return code 1 # err> error: failed to push some refs to 'https://chromium.googlesource.com/a/chromium/src' # err> hint: Updates were rejected because the remote contains work that you do # err> hint: not have locally. This is usually caused by another repository pushing # err> hint: to the same ref. You may want to first integrate the remote changes # err> hint: (e.g., 'git pull ...') before pushing again. # err> hint: See the 'Note about fast-forwards' in 'git push --help' for details. # err> ERROR:git-retry:Process failure was not known to be transient; terminating with return code 1 # err> From https://chromium.googlesource.com/a/chromium/src # err> 5e529b8..29fba81 refs/pending/heads/master -> refs/git-cl/pending/heads/master # err> remote: # err> remote: Processing changes: refs: 1 # err> remote: Processing changes: refs: 1, done # err> remote: # err> remote: ERROR: In commit c49f26bf2ae25c1b3404af752c596ffaf85ab014 # err> remote: ERROR: committer email address w3c-test-updater-bot@chromium.org # err> remote: ERROR: does not match your user account. # err> remote: ERROR: # err> remote: ERROR: The following addresses are currently registered: # err> remote: ERROR: chrome-internal-fetch@google.com # err> remote: ERROR: chrome-internal-fetch@googlers.com # err> remote: ERROR: # err> remote: ERROR: To register an email address, please visit: # err> remote: ERROR: https://chromium-review.googlesource.com/#/settings/contact # err> remote: # err> remote: # err> error: failed to push some refs to 'https://chromium.googlesource.com/a/chromium/src' # err> ERROR:git-retry:Process failure was not known to be transient; terminating with return code 1 step returned non-zero exit code: 1 @@@STEP_FAILURE@@@ https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.infra.cron%2Fw3c-test-autoroller%2F6136%2F%2B%2Frecipes%2Fsteps%2Fupdate_wpt%2F0%2Fstdout
,
Aug 11 2016
,
Aug 11 2016
You can run `git config set config.email` or something like that to change this. We do this in the recipe roller: https://cs.chromium.org/chromium/infra/recipes/recipe_modules/recipe_autoroller/api.py?l=170
,
Aug 11 2016
I thought we were doing this already, so it seems like we're probably doing something wrong ...
,
Aug 11 2016
blink-w3c-test-autoroller@chromium.org, This is the email address for the bot in code review. however, the email in the recipe is w3c-test-updater-bot@chromium.org. Should these two emails be the same?
,
Aug 11 2016
Yes.
,
Aug 11 2016
okay, I believe I can make that change to the recipe.
,
Aug 11 2016
To be clear: The user.email configured in git should match the user being used on Rietveld and also match the email address that actually has commit access. Which, in this case, is blink-w3c-test-autoroller.chromium.org .
,
Aug 11 2016
Does the user name matter? Is one user name attached to one email?? like is "W3C Autoroll Bot" associated with w3c-test-updater-bot@chromium.org?
,
Aug 11 2016
No, I don't think the user name matters, but you might as well match it if you can.
,
Aug 11 2016
,
Aug 11 2016
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra.git/+/dc5cc1ae819a49ab37a7d77241e0dd14e9fdb886 commit dc5cc1ae819a49ab37a7d77241e0dd14e9fdb886 Author: dcampb <dcampb@google.com> Date: Thu Aug 11 17:44:27 2016 Change w3c test autoroller email in recipe BUG= 636616 Review-Url: https://codereview.chromium.org/2237063002 [modify] https://crrev.com/dc5cc1ae819a49ab37a7d77241e0dd14e9fdb886/recipes/recipes/w3c_test_autoroller.expected/w3c-test-autoroller.json [modify] https://crrev.com/dc5cc1ae819a49ab37a7d77241e0dd14e9fdb886/recipes/recipes/w3c_test_autoroller.py
,
Aug 11 2016
When trying to trigger a dry run on one of the bot's cls, I received this email: "Dry run: The author blink-w3c-test-autoroller@chromium.org has not signed Google Contributor License Agreement. Please visit https://cla.developers.google.com to sign and manage CLA. https://codereview.chromium.org/2219063002/" Not exactly sure the steps to take as I do not have the password to the email account.
,
Aug 12 2016
The email addresses now match. For the issue mentioned by Dre in the comment above, I filed a separate bug: issue 637348 . |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by dcampb@google.com
, Aug 11 2016