Thanks for filing this bug,
Right now, the audio suite is scheduled nightly for ToT and weekly for builds > tot-2.
Per documentation "this test suite should be scheduled on every build for ToT, ToT-1, ToT-2"
The instructions above should be "...change it to perbuild for buildsT>=tot-2 so we can better monitor..."

From tow scheduler records at this time it should go to a single record:

[PerbuildAudio]
owner: chromeos-audio@google.com
run_on: new_build
suite: audio
branch_specs: >=tot-2
pool: suites
boards: [same list of boards]

+infra deputy

https://chromium-review.googlesource.com/c/chromiumos/infra/suite_scheduler/+/1263020 for approval
Added three newer boards too.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/infra/suite_scheduler/+/be17ddd65e24a4e71c933db7a126f7b597dbd668

commit be17ddd65e24a4e71c933db7a126f7b597dbd668
Author: Kalin Stoyanov <kalin@chromium.org>
Date: Wed Oct 10 04:14:28 2018

Move audio suite to perbuild schedule.

BUG= chromium:891985 
TEST=None

Change-Id: I43a93e7e44ffbc022c9a3704b46487a03f12bdfb
Reviewed-on: https://chromium-review.googlesource.com/1263020
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Kalin Stoyanov <kalin@chromium.org>
Reviewed-by: Cheng-Yi Chiang <cychiang@chromium.org>

[modify] https://crrev.com/be17ddd65e24a4e71c933db7a126f7b597dbd668/configs/suite_scheduler.ini

Now we can track audio suite per(-build and)-test and decide which tests can move to bvt-cq.
https://stainless.corp.google.com/search?view=matrix&row=build&col=test&days=14&suite=%5Eaudio%24&exclude_cts=false&exclude_not_run=true&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true