New issue
Advanced search Search tips

Issue 857254 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
dgarr...@chromium.org
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: ----



Sign in to add a comment

CL got picked up at next round of pfq.

Project Member Reported by xixuan@chromium.org, Jun 27 2018 
Found it from  Issue 853584 :

https://chrome-internal-review.googlesource.com/c/chromeos/autotest-cheets/+/645788 is the fix, and is chumpped in https://luci-milo.appspot.com/buildbot/chromeos/kevin-arcnext-pi-android-pfq/441.

But 441 didn't pick up this CL in autotest_package.tar, which leads to test failure. This CL gets picked up by the next round: https://uberchromegw.corp.google.com/i/chromeos/builders/kevin-arcnext-pi-android-pfq/builds/442

Why is that?

Comment 1 by dgarr...@chromium.org, Jun 28 2018 

I believe that it's because that CL required an uprev of the autotest ebuild.

The Android PFQs only uprev the ARC ebuild and nothing else, because there are constraints around multiple builders uprevving the same ebuilds. You can see this by looking for Uprev stages on that PFQ builder.

So... the Android PFQ didn't include the chumped change until the builder responsible for uprevving the autotest ebuilds finished, which is the CQ.
►

Sign in to add a comment