New issue
Advanced search Search tips

Issue 838506 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Change not being picked up by CQ

Project Member Reported by derat@chromium.org, May 1 2018

Issue description

https://crrev.com/c/1034460 has had CR+2 CQ+1 TR+1 V+1 (with pre-CQ already passed) for the last 7.5 hours, but it hasn't been picked up by the CQ in that time. https://chromiumos-status.appspot.com/ says that the tree is open.

The change appears to me to have been eligible for CQ inclusion when all of these runs started:

https://luci-milo.appspot.com/buildbot/chromeos/master-paladin/18501
https://luci-milo.appspot.com/buildbot/chromeos/master-paladin/18502
https://luci-milo.appspot.com/buildbot/chromeos/master-paladin/18503

There are no messages on it since when I added CQ+1, though.
 

Comment 1 by ihf@chromium.org, May 1 2018

Cc: ihf@chromium.org
Labels: M-68
i wonder if the precq is wedged or something.  i'm seeing stalled CLs too.

https://crrev.com/c/1034229 hasn't been picked up after 18 hours.
Investigating.
Cc: jclinton@chromium.org
Components: -Infra>Client>ChromeOS Infra>Client>ChromeOS>CI
The initial CL was eventually picked up and submitted, but there is certainly something going on.

There were multiple CQ runs that looked at it, but only actually picked up a single CL.
Most of these runs have logs like this:


02:29:59: INFO: Raw changes: CL:*612760 CL:*615228 CL:*617597 CL:*617660 CL:*617908 CL:1005564 CL:1012266 CL:1012508 CL:1012698 CL:1016130 CL:1017011 CL:1017012 CL:1017013 CL:1017014 CL:1018621 CL:1020418 CL:1020460 CL:1020981 CL:1023178 CL:1023604 CL:1023972 CL:1028223 CL:1029131 CL:1029177 CL:1031102 CL:1031103 CL:1031193 CL:1032817 CL:1033014 CL:1033614 CL:1033632 CL:1034195 CL:1034294 CL:1034374 CL:1034376 CL:1034377 CL:1034379 CL:1034380 CL:1034381 CL:1034382 CL:1034429 CL:1034460 CL:1034490 CL:1034491 CL:1034682 CL:1035425 CL:1035455 CL:1035456 CL:1036109 CL:1036195 CL:1036197 CL:1036234 CL:1036235 CL:1036236 CL:1036237 CL:1036238 CL:1036239 CL:1036240 CL:1036241 CL:1036342 CL:1036343 CL:1036344 CL:1036345 CL:1036346 CL:1036347 CL:1036348 CL:1036349 CL:1036350 CL:1036351 CL:1036352 CL:1036353 CL:1036354 CL:1036355 CL:1036356 CL:1036357 CL:1036358 CL:1036359 CL:1036360 CL:1036361 CL:1036424 CL:1036457 CL:1036472 CL:1036523 CL:1036726 CL:1036857 CL:1036865 CL:1036866 CL:967183 CL:974688 CL:979373 CL:999913
02:29:59: INFO: Filtered changes: CL:1033614


With no indication of why those CLs were filtered out. Looking at code now.


Status: Started (was: Untriaged)
Status: Assigned (was: Started)
I never did find the cause and I'm not focused on it right now. Additional logging is probably the right path forward.
Cc: gmeinke@chromium.org

Comment 9 by nxia@chromium.org, Jun 8 2018

Cc: -nxia@chromium.org

Sign in to add a comment