Grunt in cros wifi lab has not run wifi_perf suite in the last few days. https://stainless.corp.google.com/search?view=matrix&row=test&col=queued_date&first_date=2018-06-24&last_date=2018-08-20&suite=wifi_perf&board=%5Egrunt%24&exclude_cts=true&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false The host was down for couple weeks starting Aug 3rd but was brought back online last week, tracked here b/112556222 Since its been back online, it has run other wifi suites but not wifi_perf which is setup to be run nightly on ToT. https://cs.corp.google.com/chromeos_public/infra/suite_scheduler/configs/suite_scheduler.ini?l=627 DUT utilization does not seem like the bottleneck https://viceroy.corp.google.com/chromeos/dut_utilization?board=grunt&build_config=kevin-paladin&build_number=&duration=4d&experimental=False&is_locked=False&mdb_role=chrome-infra&milestone_version=&model=&pool=wificell&refresh=-1&scheduler_host=cros-full-0036&sentinel_host=chromeos-server156&staging_master=chromeos-staging-master2&status=Ready&topstreams=100&waterfall=chromeos
btw - it is currently locked, but that was done in the last hour or so http://cautotest/afe/#tab_id=view_host&object_id=8371
This might related to an issue we are suffering of master scheduler tick rate low which can result in jobs be queued for long time. See crbug.com/873815.
It should be good after our lab fully recovered. https://stainless.corp.google.com/search?view=matrix&row=test&col=queued_date&first_date=2018-08-18&last_date=2018-08-24&suite=wifi_perf&board=%5Egrunt%24&exclude_cts=true&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false
Comment 1 by harpreet@chromium.org
, Aug 20