pre-cq-launcher kicked out already verified CLs? |
|||
Issue descriptionpre-cq-launcher run: http://shortn/_fAA8NdOAS5 Tried to pick this CL up, which was already pre-cq verified, and had just been picked up by the CQ: https://chromium-review.googlesource.com/c/471526 Then it failed to create transaction because of this CL: https://chromium-review.googlesource.com/c/471456/ This resulted in the first CL (and a bunch of dependent CLs in between) getting kicked out by the pre-cq.
,
Apr 13 2017
Because CL:471526 depended on CL:471456, and CL:471456 was not qualified to be merged
,
Apr 13 2017
Re #2: How do you mean? CL:471526 was rejected incorrect by the pre-cq on April 7 5:33:06, but CL:471456 was already pre-cq verified, and had just been picked up by the CQ at that time.
,
Apr 15 2017
I was wrong in comment#2 The problem is CL:471456 wasn't picked up by the pre-cq-launcher in the 05:32:25 run. Not sure if it's because CL:471456 was picked up by the master, I didn't find the proof of the reasoning in the code actually. If this happens again, I need to add some logs and see why some CLs aren't picked up by the pre-cq-launcher.
,
Apr 18 2017
,
Mar 31 2018
likley fixed |
|||
►
Sign in to add a comment |
|||
Comment 1 by nxia@chromium.org
, Apr 13 2017