What is involved is adding multiple homo-genus android devices to each moblab setup and a version of run_suite to look up their serials, add them to the db and run the basic testbed suite.

This is seriously slowing me down.

q1) Can this be made reliable enough for the CQ?
q2) Can this coverage be gained by unit tests or virtualization?
q3) If the answer to above 2 is no, then does this even belong in the push to prod test?

Re #4.q3) In the specific case of  issue 699188 , test_push did it's job. Without the test in the push to prod test, I would have broken android testing in prod...

The reason we have this in test_push is to prevent outages, which is significantly better having nothing at all.

q2) Adding unittests is a good first step but I think a lot of the DB/RPC interactions may have to be mocked out and not have covered this. But we can investigate this.

q1) We already have a fair amount of flake with Moblab testing... this adds more complexity say should the android test devices get stuck or power down, etc.


The main reason there was a forced revert rather than wait for a simple fix was b/c there was another big outage due to the lack of AFE UI testing in the CQ and test_push. Do we plan to address that as well?

I write provide a functional end-to-end MobLab+Testbed integration test.

Whether or not it will be ran in the lab or used just locally at one's desk for verification is still open for debate.

ChromeOS Infra P1 Bugscrub.

P1 Bugs in this component should be important enough to get weekly status updates.

Is this already fixed?  -> Fixed
Is this no longer relevant? -> Archived or WontFix
Is this not a P1, based on go/chromeos-infra-bug-slo rubric? -> lower priority.
Is this a Feature Request rather than a bug? Type -> Feature
Is this missing important information or scope needed to decide how to proceed? -> Ask question on bug, possibly reassign.
Does this bug have the wrong owner? -> reassign.

Bugs that remain in this state next week will be downgraded to P2.

ChromeOS Infra P1 Bugscrub.

Issue untouched in a week after previous message. Downgrading to P2.

Hi, this bug has not been updated recently. Please acknowledge the bug and provide status within two weeks (6/22/2018), or the bug will be archived. Thank you.