[autotest] Autoserv modifications to use puppylab.
This allows us to load-test portions of our infrastructure
without requiring any physical DUTs (eg drone process counts,
scheduling jobs on DUTs, parsing results from shards to master).
What still happens:
* suites run end to end as always
* new jobs are inserted into the db via afe
* control files are staged on a devserver
* host scheduler runs as always
* jobs are scheduled according to deps on duts
* special tasks are created in the db
* autoserv for tasks just exits with 0
* test is scheduled
* Autoserv is created but simply exits after writing
job results to the appropriate directories
* parsing inserts happy results into the db
What doesn't happen:
* jobs don't ssh into DUTs in any way. Not for reset, provision,
test running etc, not for gathering. All the mock results for
a test are crafted by autoserv directly on the drone.
* DUTs don't die mysteriously or take up physical space on desk.
* bvt doesn't take 2 hours.
TEST=Ran bvt.
BUG=chromium:423225,chromium:425347
CQ-DEPEND=CL:227783
Change-Id: I5560d2a053ee45abec1b51c78a26438357e6d565
Reviewed-on: https://chromium-review.googlesource.com/228350
Tested-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Prashanth B <beeps@chromium.org>
Reviewed-by: Fang Deng <fdeng@chromium.org>
1 file changed