CQ failed to submit CLs |
|
Issue descriptionTracking bug https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/15174 Sample output (some unrelated statsd messages are interleaved?) 15:30:49: INFO: Running cidb query on pid 18401, repr(query) starts with <sqlalchemy.sql.expression.Insert object at 0x7f6e58f7d290> 15:30:55: INFO: Running cidb query on pid 18401, repr(query) starts with <sqlalchemy.sql.expression.Insert object at 0x7f6e58de6d50> 15:30:55: ERROR: unexpected error error(111, 'Connection refused') while sending data Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/statsd/connection.py", line 77, in send self.udp_sock.send(send_data) error: [Errno 111] Connection refused 15:30:56: INFO: Running cidb query on pid 18401, repr(query) starts with <sqlalchemy.sql.expression.Insert object at 0x7f6e58de6b50> 15:30:56: ERROR: Could not submit phobbs:545100:57f69ef2 15:30:59: INFO: Running cidb query on pid 18401, repr(query) starts with <sqlalchemy.sql.expression.Insert object at 0x7f6e5a0ac790> 15:30:59: ERROR: unexpected error error(111, 'Connection refused') while sending data Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/statsd/connection.py", line 77, in send self.udp_sock.send(send_data) error: [Errno 111] Connection refused 15:30:59: ERROR: Could not submit yueherngl:*400029:*acf05131 15:31:01: INFO: Running cidb query on pid 18401, repr(query) starts with <sqlalchemy.sql.expression.Insert object at 0x7f6e5906dad0> @@@STEP_FAILURE@@@ 15:31:02: ERROR: FAILED TO SUBMIT ALL CHANGES: Could not verify that changes phobbs:545100:57f69ef2 yueherngl:*400029:*acf05131 were submitted. Submitted 17 changes successfully. 15:31:02: INFO: Translating result FAILED TO SUBMIT ALL CHANGES: Could not verify that changes phobbs:545100:57f69ef2 yueherngl:*400029:*acf05131 were submitted. Submitted 17 changes successfully. to fail. 1
,
Jun 27 2017
Still need this as an annotation bug until it stops showing up as a failure
,
Jul 5 2017
I generally consider these to be Bad CL annotations, and blame them on the modified CL. |
|
►
Sign in to add a comment |
|
Comment 1 by jrbarnette@chromium.org
, Jun 27 2017These are the CLs that failed to commit: https://chrome-internal-review.googlesource.com/c/400029/ https://chromium-review.googlesource.com/#/c/545100/ Both CLs had patches uploaded to them during the CQ run. The failures are the expected behavior when that happens. Timeline: 13:36:11 - CQ run starts 14:30:33 - PS4 (new commit message) uploaded to *400029 15:00:00 - PS4 (rebase) uploaded to 545100. 15:27:53 - CQ slaves finish, and CQ starts committing changes.