It's a dut availability issue. For example, 
[WiFi_Interop_Bullhead]
run_on: weekly
day: 5
suite: android_wifi_interop
os_type: android
branches: git_nyc-release
targets: bullhead-userdebug
pool:wifichaos_bullhead

lab needs to have dut with labels:
board:android-bullhead, pool:wifichaos_bullhead
to allow suites to be created. 

Currently, there is only one dut has label board:android-bullhead
http://cautotest/afe/#tab_id=view_host&object_id=781
We need to add pool:wifichaos_bullhead label to that dut.

I have added the missing pool label for all 3 devices. Thanks Dan!

OK, reopen this if you still see issues.

I checked the nightly and it looks like he suite is listed which is good! But i do not see any runs listed. Please see - https://wmatrix.googleplex.com/unfiltered?releases=tot&suites=android_wifi_interop

I am also wondering, since these are tests against android releases, would it make sense to list it under chromeos milestones. This is probably the first suite on wmatrix for android nightly, and looks like there are still some issues.

Here are the adb hosts:
http://cautotest/afe/#tab_id=view_host&object_id=780 -- thursday
http://cautotest/afe/#tab_id=view_host&object_id=781 -- friday
http://cautotest/afe/#tab_id=view_host&object_id=782 -- saturday

Although the marlin(saturday) is down, it should have schedules something on the first 2 devices.

I don't think testbed is supported in wmatrix yet. The suite is listed because it's part of suite_scheduler.ini

You can search android_wifi_interop in cautotest, there are suite android_wifi_interop scheduled for marlin, bullhead and angler in the last couple days:
http://cautotest/afe/#tab_id=view_job&object_id=65874821
http://cautotest/afe/#tab_id=view_job&object_id=65670630
http://cautotest/afe/#tab_id=view_job&object_id=65777420

Ah ok, i see the ones you listed now! Thanks.

Both Angler and bullhead failed provisioning because of error getting `getprop sys.oem_unlock_allowed`, i will open separate issue for that.