On several CLs simultaneously, I got abort messages out of step with what happened. (Affected: crrev.com/c/942094, crrev.com/c/942093, crrev.com/c/942095).
On each, they received a CR+2 some time on March 5th. Prior to this they were V+1, CR=0, CQ=0, TR=0. This sent them to the Pre-CQ (ex: https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/pre_cq/86907), but no messages were displayed or comments added to the CLs.
Around 10:30 AM March 6th, I added CQ+1 to each. Within five minutes, each got several comments in rapid succession:
The Pre-Commit Queue has picked up your change...
The betty-pre-cq trybot for your change has timed out after 240 minutes...
Commit-Queue label set to 0 programmatically by chromite...
The moblab-generic-vm-pre-cq trybot for your change timed out after 240 minutes...
Comment 1 by pprabhu@chromium.org
, Mar 6 2018Labels: -Pri-3 Pri-1
Owner: nxia@chromium.org
Status: Assigned (was: Untriaged)