https://stainless.corp.google.com/search?view=matrix&row=queued_date&col=board_model&first_date=2018-09-21&last_date=2018-10-18&suite=%5Ewifi%5C_matfunc%24&status=GOOD&status=WARN&status=FAIL&status=ERROR&status=ABORT&status=ALERT&status=NOT_RUN&exclude_cts=true&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false

1) banjo (last run 10/11)                              ---> Locked for the move http://b/116266565 since 10/11
2) akali360 (last run 10/09)                           ---> DUT is down. 
3) peach_pi(last partial run 10/08; last full run 10/03)--> Locked for the move http://b/116266565 since 10/11. Also the DUT was in repair-failed mode after the 10/03 run.

4) pyro (very sporadic)                                ---> It is having sporadic runs due to it being locked and used for testing purpose. 
5) samus (not running complete suite)                  ---> It completed wifi_matfunc run yesterday (10/17)
6) setzer (last full run 10/04)
7) speedy (last complete run 10/06; partial run 10/10) ---> Locked for the move http://b/116266565 since 10/11
8) tiger (last run 10/03)                              ---> The autotest status is stuck. Marked it for re-verification. 
9) wolf (last run 10/10)                               ---> Locked for the move http://b/116266565 since 10/11

6) setzer  ---> The DUT is in repair-failed mode. 

Thanks for taking a look.

1) Astronaut, Bruce, and Nasher360 share chromeos-skunk-5.mtv.corp.google.com shard. The shard is seeing the following issue https://bugs.chromium.org/p/chromium/issues/detail?id=894536

2)kench/sion --> Getting marked repair failed due failure to verify servod process. 

3) nautilus  --> The device is running test. Maybe it was running other suites and didn't run wifi_matfunc
4) scarlet   --> There is no scarlet/scarlet. The model name we have is DRU (dru/scarlet), and it is running tests as expected. 

jmuppala@ - please update this bug with the latest list of boards that have not been running wifi_matfunc consistently.

1)kip-> chromeos2-row11-rack4-host6->  last ran tests on oct 25th(repair failed mode-Anthony working on it)
2)grunt ->chromeos15-row4-rack12-host2 ->running wifi release
3)daisy-spring->chromeos15-row1-rack5-host2-> need replacement (not booting out of recovery mode
4)expresso ->device not required anymore -> should remove from suite-scheduler
5)banjo-> chromeos15-row2-rack11-host5-> running wifi release