This bug should be catched from any board with ARC++. I saw many boards that I am sure should be with ARC++ in PFQ, such as, cyan, peach-pit, ....

But when I take a look at the log, e.g., 
https://uberchromegw.corp.google.com/i/chromeos/builders/cyan-chrome-pfq/builds/1251

I don't see any tests running. Will bvt-cq be executed in PFQ at all?

All the veyrons are on the pfq, just like paladins cover them

_paladin_hwtest_assignments = frozenset([
    #bvt-inline        bvt-cq            arc-bvt-cq        family
    ('veyron_mighty',  'veyron_speedy',  'veyron_minnie'), # pinky (N)

Don't know if veyron run hwtests on pfq (actually hard to find in a reasonable amount of time):

  _chrome_pfq_important_boards = frozenset([
      'veyron_minnie',
      'veyron_rialto',

Caroline runs on pfq, but it still is experimental and doesn't run hwtest yet. I would say this is a variant of issue 730296, which means we have a set of fancy builders and hardware pools for different PFQ/CQ/suites, but we don't know if they play well together.

I think I found the veyron hwtests. For now more coverage on Chrome PFQ might be obtained by landing
https://chromium-review.googlesource.com/#/c/532594/
https://chromium-review.googlesource.com/#/c/532653/

But this is all very complicated and hard to track.

sgtm. assigning to ihf since he's actually got the CLs for this

ChromeOS Infra P1 Bugscrub.

P1 Bugs in this component should be important enough to get weekly status updates.

Is this already fixed?  -> Fixed
Is this no longer relevant? -> Archived or WontFix
Is this not a P1, based on go/chromeos-infra-bug-slo rubric? -> lower priority.
Is this a Feature Request rather than a bug? Type -> Feature
Is this missing important information or scope needed to decide how to proceed? -> Ask question on bug, possibly reassign.
Does this bug have the wrong owner? -> reassign.

Bugs that remain in this state next week will be downgraded to P2.

ChromeOS Infra P1 Bugscrub.

Issue untouched in a week after previous message. Downgrading to P2.

I think it's better to keep this discussion on one bug rather than two, please split off if you think otherwise.
We had another ~.75 working day outage because the Android PFQ let in bad android this time that broke this test on the CQ: issue 797314

Chase-Pending to decide if we can have a quick CL to add android PFQ coverage.

Sorry, just move it to bvt-arc, it runs in all three places. I won't be able to do this till January. If that is not enough (due to SOC specific feature), we will have some puzzling to do.

https://chrome-internal-review.googlesource.com/#/c/chromeos/autotest-cheets/+/543061/

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/autotest-cheets/+/675d228933b01440ac4985f6ce262a6f23df0cd0

commit 675d228933b01440ac4985f6ce262a6f23df0cd0
Author: Aviv Keshet <akeshet@chromium.org>
Date: Wed Feb 21 16:44:33 2018