Current allocation:

[('pool:cts,', 13),
 ('pool:bvt,', 6),
 ('pool:chameleon_audio,', 2),
 ('pool:audio_board,', 2),
 ('pool:chameleon_hdmi,', 2),
 ('pool:wificasey_StP2,', 1),
 ('pool:wificell,', 1),
 ('pool:usb_peripherals,', 1),
 ('pool:chameleon,', 1),
 ('pool:stress,', 1)]


Looks like we may have gone overboard with cts suites.
Beyond running suites (the primary purpose) pool:suites is essential to ensure that pool:bvt has some spares.

I've transferred all the CTS DUTs back to the suites pool.

There seem to be 30 pyro and that count is not meat nor fish?

I guess there will be more in the lab at some point b/34648640. I guess CTS can wait as we have coverage with reef and snappy.

But the reason the suites pool was out is that its DUTs died over time.

> There seem to be 30 pyro and that count is not meat nor fish?

Yes, there's about 30.  They're all spoken for:
      6 bvt
      2 chameleon_hdmi
      1 faft_flashrom
      1 stress
      1 stress2
      1 stress3
     13 suites
      1 wificasey-stone
      1 wificell

Spoken for is a big word, you just moved the 13 from cts to suites.

Those units are seating in cassandra or elsewhere for platform and wifi testing.

> But the reason the suites pool was out is that its DUTs died over time.

No, the reason the suites pool was out is because every last
one of them was transferred to the CTS pool.

The standard allocation for a DVT build is 20 DUTs, 6 for bvt,
14 for suites; typically one of those gets assigned to performance
testing.  There's a separate allocation for ARC++; it hasn't
arrived yet.