+kevcheng

I don't think suite support for testbed is there yet.

It sounds like it's just an ADBHost so you can do that right now.

Scheduling a suite for a testbed (a cname entry represents multiple phones/devices) is not possible right now but is on my plate.  That work will enable running ACTS using the suite scheduler vs manually right now. 

No I think we can do this already since its not a testbed, its an adb_host

Keyword: "Single phone"

http://cautotest/afe/#tab_id=view_host&object_id=781

Bindu I think this is a WontFix :):

Look at this CL (which has been reverted as we have a better way to do this now):
https://chromium-review.googlesource.com/#/c/329974/3/suite_scheduler.ini

So for you it would look like:

[AndroidNetworkNightly]
run_on: nightly
hour: 16
suite: <suite name>
os_type: android
branches: <android branch name>
targets: <target name>
pool: suites

@Simran, i already have this CL for doing that. https://chromium-review.googlesource.com/#/c/344363/. But i filed this bug because you said in email that it was not possible to do this yet.

Ok, so with the above CL and the cl to install sl4a as part of wifi_client, i should be able to run. Is that correct ? 

I likely said its not possible for a "testbed", otherwise my mistake.

We finished this work here for a single Android/Brillo device a while back :)

I'll review the new CL later but I believe that should be it.

Cool .. Thanks for clarifying! The CL's reviewed and merged :) Thanks!

Keeping it in unconfirmed state until i have a successful run.

That CL landed... so are the suites just failing right now?

I dont see it running on wmatrix https://wmatrix.googleplex.com/unfiltered?releases=tot&suites=experimental (args_dict['add_experimental'] = True is set to true.) Am' guessing because the pools are not created yet.

I would first check to see if the tests exist on cautotest to see if they're running then check if they're reaching wmatrix.