| e0b08e6170b57f90262726eb7f04e059cb47419c |
|
11-Aug-2015 |
Hsinyu Chao <hychao@chromium.org> |
Revert "autotest: move constants to common_lib"
This reverts commit a4ac7a8f67d61f8a616724f9426dbc0fce71ce69.
BUG=chromium:519353
Change-Id: Iec2873ad22b5bb90e46a9e5b323f9626a2c07d9b
Reviewed-on: https://chromium-review.googlesource.com/292347
Reviewed-by: Hsinyu Chao <hychao@chromium.org>
Commit-Queue: Hsinyu Chao <hychao@chromium.org>
Tested-by: Hsinyu Chao <hychao@chromium.org>
Reviewed-by: Sonny Rao <sonnyrao@chromium.org>
Commit-Queue: Sonny Rao <sonnyrao@chromium.org>
Tested-by: Sonny Rao <sonnyrao@chromium.org>
/external/autotest/client/site_tests/desktopui_Respawn/desktopui_Respawn.py
|
| a4ac7a8f67d61f8a616724f9426dbc0fce71ce69 |
|
06-Aug-2015 |
Eric Caruso <ejcaruso@chromium.org> |
autotest: move constants to common_lib
This file gets imported from lots of server-side tests and
infrastructure so it shouldn't be hiding in client/cros. This
moves the file and fixes all imports.
BUG=chromium:485834
TEST=run many tests, make sure there are no problems importing
constants
Change-Id: I5c2b2a0bef6ebc998e62f40162a6ec9cc4436480
Reviewed-on: https://chromium-review.googlesource.com/291302
Trybot-Ready: Eric Caruso <ejcaruso@chromium.org>
Commit-Queue: Eric Caruso <ejcaruso@chromium.org>
Tested-by: Eric Caruso <ejcaruso@chromium.org>
Reviewed-by: Chris Sosa <sosa@google.com>
/external/autotest/client/site_tests/desktopui_Respawn/desktopui_Respawn.py
|
| 350b46b9735b286b647fdf9f1b8d09b8c41dcaa0 |
|
14-Feb-2014 |
Chris Masone <cmasone@chromium.org> |
Clear out respawn bookkeeping before/after tests that care
Some tests validate UI respawn behavior, and should make sure
that they clean up before they run as well as after to avoid
impacting other tests.
BUG=chromium:343738
TEST=desktopui_KillRestart desktopui_Respawn
STATUS=Fixed
Change-Id: Id849dcc0511d580a3e76df12dce21c449251dee5
Reviewed-on: https://chromium-review.googlesource.com/186671
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
Commit-Queue: Chris Masone <cmasone@chromium.org>
/external/autotest/client/site_tests/desktopui_Respawn/desktopui_Respawn.py
|
| 5aae68fd0a35919a5a079946df2e86a8f8da996c |
|
16-Oct-2013 |
Chris Masone <cmasone@chromium.org> |
Refer to AutoservPidAlreadyDeadError in the right package.
desktopui_Respawn incorrectly referred to utils.AutoservPidAlreadyDeadError
when the class is really in the 'error' package.
BUG=None
TEST=None
Change-Id: I65246bad1591da82128831949bdfd93d626ca38b
Reviewed-on: https://chromium-review.googlesource.com/173247
Commit-Queue: Chris Masone <cmasone@chromium.org>
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
/external/autotest/client/site_tests/desktopui_Respawn/desktopui_Respawn.py
|
| 8132ae1e3ec089c92bdab8b2e7590db8ef1023f8 |
|
14-Aug-2013 |
Chris Masone <cmasone@chromium.org> |
Update desktopui_Respawn to handle AutoservPidAlreadyDeadError
nuke_process_by_name() will now raise AutoservPidAlreadyDeadError
if it cannot find a process by the name the caller provided.
This allows the caller to gracefully handle potential raciness when
using this method in a loop. The code here in desktopui_Respawn was
not updated to tolerate this new behavior.
BUG=chromium:273118
TEST=run the test
Change-Id: If97880b35c1e0034721cfe62221d3ec7e4a64666
Reviewed-on: https://gerrit.chromium.org/gerrit/65838
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Queue: Chris Masone <cmasone@chromium.org>
/external/autotest/client/site_tests/desktopui_Respawn/desktopui_Respawn.py
|
| 7d6af6852fcfdb956e4723eb076e10533f48d3f2 |
|
06-Aug-2013 |
Chris Masone <cmasone@chromium.org> |
Add desktopui_CrashyReboot{Server} autotest
To address some GPU hanging problems, we added logic to reboot the
device if the UI seemed to crash too much, too often.
This server-side test validates this logic by deploying an
associated client-side test to the DUT that drives it into
the failure state.
CQ-DEPEND=CL:65243
BUG=chromium:261784
TEST=run this autotest, and it should succeed.
TEST=run this autotest and while it's running, echo $(date +%s) > /var/lib/ui/reboot-timestamps. The test should fail.
Change-Id: I68af57e0266e85434ad63e1f646e90a41a6d393d
Reviewed-on: https://gerrit.chromium.org/gerrit/65218
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Queue: Chris Masone <cmasone@chromium.org>
/external/autotest/client/site_tests/desktopui_Respawn/desktopui_Respawn.py
|
| 545acb42da0c358dea4a3279408cca1f67d1cd4e |
|
02-Aug-2013 |
Chris Masone <cmasone@chromium.org> |
Add new autotest for UI respawning behavior
Since we moved UI respawning management into a separate job,
instead of using the default upstart behavior, we need a test
to validate that it works.
CQ-DEPEND=I5c15f2e99e26defb1458ca2d6b23721fd181ef06
BUG=chromium:261784
TEST=run desktopui_Respawn
Change-Id: Iba61ecf10319f07ef6ed7a1d5204ecdb368fcbef
Reviewed-on: https://gerrit.chromium.org/gerrit/64663
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Queue: Chris Masone <cmasone@chromium.org>
/external/autotest/client/site_tests/desktopui_Respawn/desktopui_Respawn.py
|