These are scheduled to run in the bvt pool

07:26:25: INFO: RunCommand: /b/c/cbuild/repository/chromite/third_party/swarming.client/swarming.py run --swarming chromeos-proxy.appspot.com --task-summary-json /tmp/cbuildbot-tmpxKx_x2/tmpTdW_EY/temp_summary.json --raw-cmd --task-name sand-release/R64-10060.0.0-paygen_au_dev --dimension os Ubuntu-14.04 --dimension pool default --print-status-updates --timeout 14400 --io-timeout 14400 --hard-timeout 14400 --expiration 1200 '--tags=priority:Build' '--tags=suite:paygen_au_dev' '--tags=build:sand-release/R64-10060.0.0' '--tags=task_name:sand-release/R64-10060.0.0-paygen_au_dev' '--tags=board:sand' -- /usr/local/autotest/site_utils/run_suite.py --build sand-release/R64-10060.0.0 --board sand --suite_name paygen_au_dev --pool bvt --file_bugs True --priority Build --timeout_mins 180 --retry True --suite_min_duts 2 --job_keyvals "{'cidb_build_stage_id': 59990285L, 'cidb_build_id': 1971875, 'datastore_parent_key': ('Build', 1971875, 'BuildStage', 59990285L)}" -c

Sand is slow because it has no shard.

Both poppy and sand need shards:
    $ BOARDS=( $(atest host list -b pool:bvt | count_labels -b | awk '{print $2}') )
    $ for b in ${BOARDS[@]}; do atest shard list 2>/dev/null | grep -q $b || echo $b; done
    poppy
    sand

... It's likely cheaper to do them both at the same time.

Provisionally assigning to secondary as a routine task, but I may take it up if I get cycles.

Both added to chromeos-skunk-4.mtv.corp.google.com