test_push error when sending email |
||
Issue description[chromeos-staging-master2.hot.corp.google.com] out: Instructions for pushing to prod are available at https://goto.google.com/autotest-to-prod [chromeos-staging-master2.hot.corp.google.com] out: INFO:googleapiclient.discovery:URL being requested: POST https://www.googleapis.com/gmail/v1/users/me/messages/send?alt=json [chromeos-staging-master2.hot.corp.google.com] out: INFO:oauth2client.client:Refreshing due to a 401 (attempt 1/2) [chromeos-staging-master2.hot.corp.google.com] out: INFO:oauth2client.client:Refreshing access_token [chromeos-staging-master2.hot.corp.google.com] out: DEBUG:root:ending retries with error: <class 'googleapiclient.errors.HttpError'>(<HttpError 400 when requesting https://www.googleapis.com/gmail/v1/users/me/messages/send?alt=json returned "Invalid to header">) [chromeos-staging-master2.hot.corp.google.com] out: INFO:root:Waiting for ts_mon flushing process to finish... [chromeos-staging-master2.hot.corp.google.com] out: INFO:root:Finished waiting for ts_mon process. [chromeos-staging-master2.hot.corp.google.com] out: Traceback (most recent call last): [chromeos-staging-master2.hot.corp.google.com] out: File "./site_utils/test_push.py", line 698, in <module> [chromeos-staging-master2.hot.corp.google.com] out: sys.exit(main()) [chromeos-staging-master2.hot.corp.google.com] out: File "./site_utils/test_push.py", line 695, in main [chromeos-staging-master2.hot.corp.google.com] out: return _main(arguments) [chromeos-staging-master2.hot.corp.google.com] out: File "./site_utils/test_push.py", line 687, in _main [chromeos-staging-master2.hot.corp.google.com] out: message) [chromeos-staging-master2.hot.corp.google.com] out: File "./site_utils/test_push.py", line 590, in send_notification_email [chromeos-staging-master2.hot.corp.google.com] out: gmail_lib.send_email(','.join(email_list), title, msg) [chromeos-staging-master2.hot.corp.google.com] out: File "/usr/local/autotest/site_utils/gmail_lib.py", line 177, in send_email [chromeos-staging-master2.hot.corp.google.com] out: backoff_factor=RETRY_BACKOFF_FACTOR) [chromeos-staging-master2.hot.corp.google.com] out: File "/usr/local/autotest/site-packages/chromite/lib/retry_util.py", line 244, in GenericRetry [chromeos-staging-master2.hot.corp.google.com] out: return _run() [chromeos-staging-master2.hot.corp.google.com] out: File "/usr/local/autotest/site-packages/chromite/lib/retry_util.py", line 177, in _Wrapper [chromeos-staging-master2.hot.corp.google.com] out: ret = func(*args, **kwargs) [chromeos-staging-master2.hot.corp.google.com] out: File "/usr/local/autotest/site-packages/chromite/lib/retry_util.py", line 243, in _run [chromeos-staging-master2.hot.corp.google.com] out: return functor(*args, **kwargs) [chromeos-staging-master2.hot.corp.google.com] out: File "/usr/local/autotest/site_utils/gmail_lib.py", line 155, in _run [chromeos-staging-master2.hot.corp.google.com] out: client.send_message(m, ignore_error=False) [chromeos-staging-master2.hot.corp.google.com] out: File "/usr/local/autotest/site_utils/gmail_lib.py", line 121, in send_message [chromeos-staging-master2.hot.corp.google.com] out: userId='me', body=message.get_payload()).execute() [chromeos-staging-master2.hot.corp.google.com] out: File "/usr/local/autotest/site-packages/chromite/third_party/oauth2client/util.py", line 140, in positional_wrapper [chromeos-staging-master2.hot.corp.google.com] out: return wrapped(*args, **kwargs) [chromeos-staging-master2.hot.corp.google.com] out: File "/usr/local/autotest/site-packages/chromite/third_party/googleapiclient/http.py", line 838, in execute [chromeos-staging-master2.hot.corp.google.com] out: raise HttpError(resp, content, uri=self.uri) [chromeos-staging-master2.hot.corp.google.com] out: googleapiclient.errors.HttpError: <HttpError 400 when requesting https://www.googleapis.com/gmail/v1/users/me/messages/send?alt=json returned "Invalid to header"> This fails an otherwise successful test_push.
,
Jan 22 2018
Fixed I think?
,
Jan 22 2018
Yes, I killed that email altogether. |
||
►
Sign in to add a comment |
||
Comment 1 by pprabhu@chromium.org
, Dec 22 2017