There are 14 tests part of the platform_ExternalUsbPeripherals versions.
We are running 8 out of these 14 - https://screenshot.googleplex.com/210px1as9tn
Having other suite(s) are running on the same pool, there is quite a bit autotest overhead, that can limit the bandwidth.
Also from efficiency stand point we should probably not run some tests that are part of others.
Some should be removed as they are outdated.
1) Remove control files that we have no intent to use (anymore), like:
- control.printer
- control.stress2
- control.stress3
- control.usb_detect.crashes
2) Remove control files that are redundant, like:
- control.detect.login_unplug_plug
- control.detect.reboot_login
- control.detect.unplug_plug
3) Further having we are to consolidate some series of tests we can remove the following
- CLOSE_LID based
control.detect.login_closelid_openlid
control.detect.login_closelid_unplug_openlid_plug
control.detect.login_unplug_closelid_plug_openlid
- SUSPEND_RESUME based
control.detect.login_suspend_resume
control.detect.login_suspend_unplug_resume_plug
control.detect.login_unplug_suspend_plug_resume
control.detect.login_unplug_suspend_resume_plug
4) Other suggestions
- We can try adding LOGOUT step
- We can combine suspend-resume and close_lid-open_lid (like the real scenario - left the laptop to suspend and then close the lid to commute to work)
As a result we can form no more than 4 scenarios we can use for perbuild suite runs.
If we need some other, like tracking crashes, or repetitive/stress types of tests, we can put add to nightly or weekly schedule.
Comment 1 by ka...@chromium.org
, Nov 1Prasanthi, please proceed with 1) and 2) Matt, proceed with 3) and remove these files, but add scenarios like - consolidated long cycle of combined steps like: default_actions = str("reboot,plug,unplug," "login,plug,unplug," "reboot,plug,login,unplug,plug," "reboot, unplug,login,plug" "suspend,resume," "unplug,suspend,plug,resume," "suspend,unplug,resume,plug") I tested this one. It has 25 steps and PASSed in ~15 min. - one crash checking shorter cycle like default_actions = str("plug,unplug,login,plug,unplug, "suspend,plug,resume,suspend,unplug,resume") - one lid close open shorter cycle like default_actions = str("plug,unplug,login,plug," "closelid,unplug,openlid," "closelid,plug,openlid,unplug") Sridhar, lets implements the LOGOUT step. This was done before by posting(touch) the temp file /tmp/simple_login_exit when the Login client test is called without 'exit_without_logout=True'. LMK what you think