Code review comment for lp://qastaging/~liuyq0307/lava-lab/keep-one-fastmodel-per-node
Revision history for this message
| Amit Pundir (pundiramit) wrote | # |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
Dave, Matt,
I understand your concern but over the period of time we have found that running multiple fastmodels on a single machine put extra load on that machine. Random adb connection failures are also observed rather frequently on machines running multiple models.
It is "OK" to run regular kernel and system tests, which run for about 2-3 hours in total, on multiple models sharing a single machine but CTS tests (one of which run for 20 hours straight) are very prone to this extra load and they tend to reboot models when they timeout due to inactivity or just skip running remaining tests. We have observed this on local setups as well.
We just want to make sure that we run the tests (CTS and Monkey in particular) to completion. Ideally it would be great to have one more machine in the lab dedicated to fastmodels so that we don't have backlog of jobs.
Thanks.