| 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/cros/login.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/cros/login.py
|
| 3d68fe8213ef86684d7911f889d56d1345bf3272 |
|
26-Mar-2014 |
Chris Masone <cmasone@chromium.org> |
Listen for ownership-taken signal on DBus
Many tests that touch on device Ownership were using a
function that simply watched for the presence of policy
and owner key files to indicate that the session_manager
had completed the ownership-taking process on the sign-in
of the first user. This could be tricked, though, in the
case of the UI being restarted between the test clearing
these files and then checking for them again. Stop using
this and switch to watching for signals announcing that
ownership has been taken, which the session_manager has
sent all along anyhow.
BUG=chromium:355664
TEST=login_*Ownership*
Change-Id: I54000c426cfb1aef8fd1518f9cdadec2b42c6500
Reviewed-on: https://chromium-review.googlesource.com/194142
Reviewed-by: Chris Masone <cmasone@chromium.org>
Commit-Queue: Chris Masone <cmasone@chromium.org>
Tested-by: Chris Masone <cmasone@chromium.org>
/external/autotest/client/cros/login.py
|
| 84890bdbda01c0b31ef2f4fb9348aff0c0128add |
|
21-Feb-2014 |
J. Richard Barnette <jrbarnette@chromium.org> |
Handle UI restart without removing login-prompt-visible.
This changes the cros_ui.start() and cros_ui.restart() functions
not to remove the login-prompt-visible timestamp file. Instead,
they detect a new login prompt by watching for changes in the
output of "bootstat_get_last login-prompt-visible".
This also changes CrosHost._restart_ui() to use the same basic
algorithm as cros_ui. The new implementation doesn't need to
install Autotest, and doesn't use cros_ui private interfaces.
BUG=chromium:344955,chromium:345012
TEST=run BVT, log in, run bootstat_summary, see full history
TEST=run a cleanup job in a local autotest install, see restart in logs
Change-Id: Ic53314e1bc8ced524d750fcfcbd3bf0bb0be39ff
Reviewed-on: https://chromium-review.googlesource.com/187439
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Richard Barnette <jrbarnette@chromium.org>
/external/autotest/client/cros/login.py
|
| fa71bb873fac1f1679685d417b2a4272d22af9c7 |
|
30-May-2013 |
Mike Frysinger <vapier@chromium.org> |
client tests: fix pgrep usage
The current autotest code runs pgrep with fd 1 (stdout) and fd 2 (stderr)
closed. Not redirected to /dev/null, but straight up closed.
For older versions, pgrep wouldn't complain and would happily exit(0):
write(1, "31396\n31398\n31400\n31405\n31425\n31"..., 42) = -1 EBADF (Bad file descriptor)
exit_group(0)
But the newer version checks the return value of the write() which causes
it to fail and exit(1) when it otherwise worked:
write(1, "31396\n31398\n31400\n31405\n31425\n31"..., 42) = -1 EBADF (Bad file descriptor)
close(1) = -1 EBADF (Bad file descriptor)
write(2, "pgrep-3.3: ", 11) = -1 EBADF (Bad file descriptor)
write(2, "write error", 11) = -1 EBADF (Bad file descriptor)
write(2, ": Bad file descriptor", 21) = -1 EBADF (Bad file descriptor)
exit_group(1)
This is arguably bad behavior in autotest as it shouldn't run random
programs with stdout/stderr completely disconnected.
We could use utils.run and utils.system, but those both end up logging
all the output and making things noisy. So just redirect stdout to
/dev/null manually.
BUG=chromium:221806
TEST=`cbuildbot {arm,amd64,x86}-generic-full` passes vmtests w/new & old procps versions
Change-Id: I020f5f1b2d2fd3d9b9df5704eed12103ee803fa0
Reviewed-on: https://gerrit.chromium.org/gerrit/57073
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Mike Frysinger <vapier@chromium.org>
/external/autotest/client/cros/login.py
|
| 6cb26ad178990814fce3209c464afe7f131ec5b0 |
|
21-May-2013 |
Elly Fong-Jones <ellyjones@chromium.org> |
[autotest] remove dependencies on /home/chronos/user
BUG=chromium:212419
TEST=suite_Smoke
Change-Id: I8849e3eb6e76a3a3358422f1c2269a926d35994f
Signed-off-by: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/56050
Reviewed-by: Will Drewry <wad@chromium.org>
/external/autotest/client/cros/login.py
|
| 5d010aa50a0694d498e8317fd8044e56474ce7ed |
|
06-May-2013 |
Chris Masone <cmasone@chromium.org> |
Add multiprofile tests for session_manager.StartSession()
Multiple calls to StartSession() with different users should be allowed,
while multiple calls with the same user should not.
BUG=chromium:235179
TEST=run these new tests
CQ-DEPEND=I1200c4463d43cd8cf7d49a2f9f0667ac1cccc261
CQ-DEPEND=I5ee9fb18e1f8c1a933b899acc62618323f2df9bf
Change-Id: I912d3ded053a7f0f41c604f5ffef15477d634017
Reviewed-on: https://gerrit.chromium.org/gerrit/50223
Commit-Queue: Chris Masone <cmasone@chromium.org>
Reviewed-by: Chris Masone <cmasone@chromium.org>
Tested-by: Chris Masone <cmasone@chromium.org>
/external/autotest/client/cros/login.py
|
| 64c42128a4ecf3c36dd47c6aad1c05c3d51d318c |
|
08-Nov-2012 |
David James <davidjames@chromium.org> |
Wait for Chrome to generate crash dumps before sending SIGBUS.
In cases where Chrome fails to logout, this may have been because of a crash.
Generating crash dumps may take a while, especially if the system is loaded,
and local tests have shown that this process often takes longer than the
typical 45-second pyauto timeout.
Rather than increase the general timeout for logout, I've updated autotest to
wait a bit before sending the SIGBUS signal. If Chrome exits on its own, then
we'll get a nice crash dump and there is no need to send a SIGBUS.
Also move common logic for creating a LogReader into login.wait_for_condition.
BUG=chromium-os:36142
TEST=Currently running remote trybot runs to reproduce crash and verify that
this logic works. repo grep to make sure all cases of wait_for_condition
were updated.
Change-Id: I3b7a2ba4fc2b6be248d321cdb7b7ec6f407c1e01
Reviewed-on: https://gerrit.chromium.org/gerrit/37595
Commit-Ready: David James <davidjames@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: David James <davidjames@chromium.org>
/external/autotest/client/cros/login.py
|
| b6d2993fb77f771a886c41ace0850773f5498bed |
|
11-Apr-2012 |
barfab@chromium.org <bartfab@chromium.org> |
Fix includes, unbreaking PyAuto functional and improving style
* Ensure "common" is imported whenever "autotest_lib.client" is used.
* Remove unnecessary "autotest_lib.client.cros" prefix from includes.
* Remove hashbang lines from files that cannot be run from the
command line anyway.
* Improve autotest style guide conformance:
-> Reorder includes into groups and alphabetically within these.
-> Lump together includes in each group.
BUG=chromium-os:29150
TEST=desktopui_PyAutoFunctionalTests.CHROMEOS_POLICY
TEST=desktopui_PyAutoFunctionalTests.FULL, suite:bvt
Change-Id: I87479ed729bca38888e4bcf250cf7997406387e5
Reviewed-on: https://gerrit.chromium.org/gerrit/19886
Commit-Ready: Bartosz Fabianowski <bartfab@chromium.org>
Reviewed-by: Bartosz Fabianowski <bartfab@chromium.org>
Tested-by: Bartosz Fabianowski <bartfab@chromium.org>
/external/autotest/client/cros/login.py
|
| 6432b54982c60c89d773f31edb86b465169afe34 |
|
04-Apr-2012 |
Nirnimesh <nirnimesh@chromium.org> |
Get rid of obsolete wait_for_initial_chrome_window() function
wait_for_initial_chrome_window() and refresh_window_manager() are redundant
to me since there's no window manager anymore so chrome can authoratatively
tell if the initial chrome window is up and ready, which it is for all UI tests.
BUG=None
TEST=None
Change-Id: If5404b39a1e84cf3ecb6647e8e19fa46193e6b2b
Reviewed-on: https://gerrit.chromium.org/gerrit/19606
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Tested-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Ready: Mitsuru Oshima <oshima@chromium.org>
/external/autotest/client/cros/login.py
|
| 5c37463bb75ff025af20eac152c12af6ccbf7ccf |
|
05-Apr-2012 |
barfab@chromium.org <bartfab@chromium.org> |
Teach autotest_lib about per-user mounts and ephemeral users
This CL improves the utility methods for writing cryptohome tests so that
they can deal with per-user mount points and recoginize ephemeral user
cryptohomes backed by tmpfs correctly. The unmount_vault() method remains
to be updated when umount requests are made per-user as well.
All cryptohome tests are updated and verified to work in the current
hybrid world where per-user mount points and the shared mount point
coexist. Once concurrent per-user mounts are actually deployed, some of
the tests may need further tweaking.
As a final improvement, three cryptohome tests that were slated for the
bvt suite but accidentally dropped off the radar are fixed up and added
to the suite.
BUG=chromium-os:29003
TEST=all affected pyauto tests: login_Cryptohome*, platform_Cryptohome*,
TEST=logging_LogVolume, security_ProfilePermissions
Change-Id: Ib8301844e72ef3901889cce91fd58c9e06ce0a65
Reviewed-on: https://gerrit.chromium.org/gerrit/19668
Reviewed-by: Elly Jones <ellyjones@chromium.org>
Commit-Ready: Bartosz Fabianowski <bartfab@chromium.org>
Tested-by: Bartosz Fabianowski <bartfab@chromium.org>
/external/autotest/client/cros/login.py
|
| d51ac9cdab93aee5b408dde4543a00d9913f740f |
|
10-Sep-2011 |
David James <davidjames@chromium.org> |
Refactor tests to consistently wait for login prompt to show up after logout.
This CL refactors the autotest suite to consistently check for the login prompt
visibility whenever the session manager is killed. This ensures that the Window
Manager can depend on being fully initialized prior to being killed.
BUG=chromium-os:18919
TEST=Ran trybot run with VM tests.
Change-Id: I1747bc55c66c3eeae10e2cafa2dfc8219d758874
Reviewed-on: http://gerrit.chromium.org/gerrit/8184
Commit-Ready: David James <davidjames@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: David James <davidjames@chromium.org>
/external/autotest/client/cros/login.py
|
| 8592a64bbc47c265947fb62a0f410567bce51291 |
|
02-Sep-2011 |
Nirnimesh <nirnimesh@chromium.org> |
Fix restart_session_manager to work with webui login
Automation using pyauto does not need to verify for pixels on the screen.
Will work with nativeui login as well.
BUG=chromium-os:19639
TEST=suite_Smoke
Change-Id: Ia9d7200d3216844132275c1090be1db7c7453b30
Reviewed-on: http://gerrit.chromium.org/gerrit/7225
Reviewed-by: Zelidrag Hornung <zelidrag@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Tested-by: Xiyuan Xia <xiyuan@chromium.org>
/external/autotest/client/cros/login.py
|
| 300653349ae95b380dd5201a9a964b33f9fc90d8 |
|
31-Aug-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Extend timeout for session manager restart to 90 secs.
Extends the timeout to 90 seconds to account for 60 sec session_manager
timeout + 15 sec core dump time.
BUG=none
TEST=Ran smoke.
Change-Id: I2b9515e6fc357802c3dd5d1b16aa195ac0eb26f0
Reviewed-on: http://gerrit.chromium.org/gerrit/7050
Tested-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
/external/autotest/client/cros/login.py
|
| b48fd370bf624fcaf54fbf696d8dfa1852ad5d56 |
|
19-Aug-2011 |
Nirnimesh <nirnimesh@chromium.org> |
Do not bother to logout at the end of tests based on cros_ui_test
Each cros_ui_test based test begins with a fresh ui instance anyway.
Saves some time per test.
BUG=None
TEST=suite_Smoke
Change-Id: Ic92353bd981bb9334b4fecf85f0f4033f17373a6
Reviewed-on: http://gerrit.chromium.org/gerrit/6295
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Chris Masone <cmasone@chromium.org>
Tested-by: Nirnimesh <nirnimesh@chromium.org>
/external/autotest/client/cros/login.py
|
| f77fa8e0abc40604e740c82a608d4db9d7665f0d |
|
28-Jul-2011 |
Nirnimesh <nirnimesh@chromium.org> |
Replace autox login calls with pyauto calls
All login calls made through cros_ui_test.py now go thru pyauto.
This is in preparation for switching the default login behavior to webui with
gaia extension login.
Also:
- works native login ui. Will be expanded for webui login crosbug.com/18271
- reduces dep on some magic files (like LOGGED_IN_MAGIC_FILE, ownership)
- wholesale conversion of tests in BVT to use pyauto
- bring pyauto goodness to mainstream autotest
I've tried most tests from different autotest suites.
BUG=chromium-os:17904
TEST=smoke suite, BVT, regression suite
Change-Id: Ib31d7137ed1a757cc238168c84d779d0fbaea15a
Reviewed-on: http://gerrit.chromium.org/gerrit/4929
Reviewed-by: Nirnimesh <nirnimesh@chromium.org>
Tested-by: Nirnimesh <nirnimesh@chromium.org>
/external/autotest/client/cros/login.py
|
| a7fb896dfe7cd4f0d7a9e8cd3efa3bf5a2ad2330 |
|
17-Aug-2011 |
Gaurav Shah <gauravsh@chromium.org> |
autotest: Make poll_for_condition log the error before raising an exception
When a test fails or errors out (via raising one of the derived TestError or
TestFail exceptions), autotest displays the <test name>.ERROR log file to help
debug the reason for the test failure.
Many of our test failures are caused due to timeouts while waiting for a
condition using poll_for_condition and these do not get logged to the ERROR log
file.
This CL adds a logging.error call with the error description to
poll_for_condition before the exception is raised to signify test failure. Also
added logging to a couple of other places where some custom TestError exceptions
are raised.
BUG=none
TEST=Caused a deliberate timeout failure on login_CryptohomeMounted by reducing the timeout
to a very small value. The test ERROR file now contained the timeout error message.
Change-Id: I4915e2dd3eaf72de562c0ccf53429b8ed8f6bf04
Reviewed-on: http://gerrit.chromium.org/gerrit/6115
Reviewed-by: Chris Masone <cmasone@chromium.org>
Tested-by: Gaurav Shah <gauravsh@chromium.org>
/external/autotest/client/cros/login.py
|
| 6db3f80ab78c4cb2d3b09378add10236dd412153 |
|
12-Aug-2011 |
Daniel Erat <derat@chromium.org> |
autotest: Wait for login to finish before logging out.
This makes login.attempt_logout() call
wait_for_initial_chrome_window() before asking the session
manager to stop the session. I'm hoping that this will
avoid a bunch of Chrome and window manager crashes that
we've seen when the UI job is stopped soon after it's been
started.
BUG=chromium-os:17899,chromium-os:18269
TEST=ran suite_Smoke a few times without seeing any chrome crashes (i was seeing them consistently in login_CryptohomeMounted and login_CryptohomeUnmounted before)
Change-Id: I80d3d6aaa0db5b7a12f973d114270a7f23d324a1
Reviewed-on: http://gerrit.chromium.org/gerrit/5797
Reviewed-by: Dave Moore <davemoore@chromium.org>
Tested-by: Daniel Erat <derat@chromium.org>
/external/autotest/client/cros/login.py
|
| f522d34bae441faab7d506087f1d64d3adcf162e |
|
10-Aug-2011 |
Chris Masone <cmasone@chromium.org> |
Autotest should also wait for potential chrome crashes
We updated the session manager to wait for a potentially time-consuming chrome
core dump operation on logout, but not autotest.
BUG=chromium-os:18966
TEST=suite_Smoke
STATUS=Verified
Change-Id: I1ae0eaf415293be03e2890eebec1926249fc8472
Reviewed-on: http://gerrit.chromium.org/gerrit/5660
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-by: Chris Masone <cmasone@chromium.org>
/external/autotest/client/cros/login.py
|
| b6dc2fc4495f0f2bef30153a60005dabadda81fb |
|
04-Jun-2011 |
David James <davidjames@chromium.org> |
Fix typo in "ensure that pgrep failure doesn't kill the tests".
"except e" -> "except Exception as e"
The following error was reported in the smoke suite:
Traceback (most recent call last):
...
File "/usr/local/autotest/cros/login.py", line 331, in nuke_login_manager
nuke_process_by_name('session_manager')
File "/usr/local/autotest/cros/login.py", line 338, in nuke_process_by_name
except e:
NameError: global name 'e' is not defined
BUG=chromium-os:16154
TEST=test on buildbots
Change-Id: I478c5edf77efca69e689ea1c003218aa039e3e40
Reviewed-on: http://gerrit.chromium.org/gerrit/2146
Reviewed-by: Ryan Cui <rcui@chromium.org>
Tested-by: Ryan Cui <rcui@chromium.org>
/external/autotest/client/cros/login.py
|
| 9f9abae12629eead0082b2d73621f54e5fe6725d |
|
02-Jun-2011 |
Chris Masone <cmasone@chromium.org> |
[autotest] ensure that pgrep failure doesn't kill the tests
If we're trying to nuke a process, and it's already not there, that's fine. Just return.
BUG=None
TEST=suite_Smoke
Change-Id: Ie474dea0a45abf62e732480a7fa68dca3056f7fe
Reviewed-on: http://gerrit.chromium.org/gerrit/1940
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
/external/autotest/client/cros/login.py
|
| 97ac25e78f6245a0287432fdf56507dc7864c1da |
|
12-May-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Instead of killing session manager. Send StopSession() via dbus.
BUG=chromium-os:15235
TEST=Ran smoke, bvt.
Change-Id: I6daa10b0c9dd4b521f198514fa6d4cb5eb726666
Reviewed-on: http://gerrit.chromium.org/gerrit/736
Reviewed-by: Chris Masone <cmasone@chromium.org>
Tested-by: Dale Curtis <dalecurtis@chromium.org>
/external/autotest/client/cros/login.py
|
| 105706efb7ebc97575dafd7a92bb815f79d8bb47 |
|
29-Apr-2011 |
Chris Masone <cmasone@chromium.org> |
[autotest] Add test for the re-taking of ownership after the owner key is lost
BUG=chromium-os:11193
TEST=run this test
Change-Id: I95b402d47ec430a8556d012d9a2ee2614507a1e4
Review URL: http://codereview.chromium.org/6880288
/external/autotest/client/cros/login.py
|
| 80130412744f93953ac04a38b6ed04cc18e025a6 |
|
22-Apr-2011 |
Chris Masone <cmasone@chromium.org> |
[autotest] Move Ownership tests to regression suite
BUG=chromium-os:12846
TEST=suite_Smoke no longer runs OwnershipTaken and OwnershipNotRetaken
Change-Id: I33a6b934d9bd00d0fcdbf4658fa80a22dc17d851
R=sonnyrao@chromium.org
Review URL: http://codereview.chromium.org/6896021
/external/autotest/client/cros/login.py
|
| 52e1040246824993636a81eee914d0e68778e748 |
|
05-Apr-2011 |
Gaurav Shah <gauravsh@chromium.org> |
This avoids the key generation wait as part of performing ownership on the device.
Change-Id: Id5c074721730320e42442480ce534c9f460d476d
BUG=chromium-os:12846
TEST=manual (see below)
Multiple runs of suite_Smoke without any time outs. Manual inspection of logs to verify that ownership was not being taken unless the test (login_OwnershipTaken, login_OwnershipNotRetaken) requested it.
Review URL: http://codereview.chromium.org/6757001
/external/autotest/client/cros/login.py
|
| 43c777916d5567c3dc508602f6a7ccf231a91967 |
|
29-Mar-2011 |
Gaurav Shah <gauravsh@chromium.org> |
Fix faulty renice: -ve priority numbers mean more scheduling priority.
Get rid of re-nice completely since it is not needed.
BUG=chromium-os:12846
TEST=(man renice)
Change-Id: I664bfe643c0ad682605505de03abaf6eeb184985
Review URL: http://codereview.chromium.org/6719026
/external/autotest/client/cros/login.py
|
| 93e65d0badb3e0bf25b5c499b683ba6440208d2b |
|
10-Mar-2011 |
Chris Masone <cmasone@chromium.org> |
[autotest] Update ChromeSession to play nicely with modern chrome os
The ChromeSession class was written long ago, at a time before we'd
picked a permanent mount point for cryptohomes, or written code to
drive a login for testing purposes, or written a base class from which
all UI tests are supposed to inherit, or made assumptions around there
being just one instance of chrome running at any given time.
This changelist updates the class to be compatible with these assumptions,
and updates tests that use this class to work in the New World Order :-)
BUG=12697
TEST=Run the affected tests, and ensure that no more of them fail than did before this CL
Change-Id: I518a4e45d0a72beeed22df3e31817fe9642dc1a0
Review URL: http://codereview.chromium.org/6624002
/external/autotest/client/cros/login.py
|
| a2e8d3b465cd49051be4fa8cf2c8f0608da94721 |
|
08-Mar-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Double ownership timeout to 60 seconds.
Owner key generation can exceed the alotted timeout on machines which have insufficient entropy for key generation. Lab machines with rare phyical interaction are especially susceptible.
Some /sbin/keygen numbers for a Cr-48 over 3 runs on 28 machines: min: 1.519s, max: 32.524s, avg 8.48s. Other boards had numbers ranging up to 42 seconds.
Change-Id: I24c11deb20b44b2e81df89e3a0f77dbce903d0a2
BUG=chromium-os:12846
TEST=Ran several login based tests.
Review URL: http://codereview.chromium.org/6628075
/external/autotest/client/cros/login.py
|
| 8af5c779fcfd36cb108202cd41c7c33ab1acfa30 |
|
01-Mar-2011 |
Chris Masone <cmasone@chromium.org> |
[autotest] Only wait for ownership to be taken during _real_ logins
After fixing 12574, we will no longer try to take ownership on Guest login -- which is right.
This make the test logic no longer wait for ownership on Guest logins, to match up with the
new, correct, behavior.
BUG=12574
TEST=suite_Smoke
Change-Id: Icd12c5d372b5b68c7f7928a2da859ce5a4679c7a
Review URL: http://codereview.chromium.org/6597081
/external/autotest/client/cros/login.py
|
| 0405508cf785f06c48d2506bf76e4f385c9b649d |
|
01-Mar-2011 |
Chris Masone <cmasone@chromium.org> |
[autotest] Wait for ownership during CryptohomeMounted test
if we dont wait for ownership to complete after login, then we can
wind up sigabrting the tool that takes ownership, leading to test
failures.
BUG=12616
TEST=suite_Smoke
STATUS=Fixed
Change-Id: I5d22fb1e8571bec8a78297fa894861b7591e635d
Review URL: http://codereview.chromium.org/6602035
/external/autotest/client/cros/login.py
|
| cfa8a60acd8894d174037dff14f1076705883ade |
|
22-Feb-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Up process priority during login.
We're seeing replicated characters during login which cause login failures. The general suspicion is autox being descheduled between KeyPress and KeyRelease events. Testing with increased priority caused the login failures to disappear. Sadly the occassional login timeout error seems unaffected.
Also removed Tab between fields per old todo since Alt+P is available to focus the password field now.
Change-Id: I44a431df1d27831075c5a9f198f8ee5848f586f5
BUG=chromium-os:12265
TEST=Ran 30 login_LoginSuccess tests and a couple bvt runs.
Review URL: http://codereview.chromium.org/6546062
/external/autotest/client/cros/login.py
|
| 44d8a98858aa86e9a719d418a4675b150be3c060 |
|
16-Feb-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Don't log chrome SIGABRT crashes during logout.
Per discussion with cmasone, SIGABRT crashes should be ignored during logout.
BUG=chromium-os:12100
TEST=Ran run_remote_tests w/ good build and bad build.
Review URL: http://codereview.chromium.org/6525034
Change-Id: I29f6e92ba41de64094fe6a36889bacc49445ba36
/external/autotest/client/cros/login.py
|
| 9933ab84a71a3bab32cf8e06fbf99b2abef36922 |
|
14-Jan-2011 |
Chris Masone <cmasone@chromium.org> |
[autotest] Add an autotest to ensure that ownership can be taken
BUG=6085
TEST=this is the test!
Change-Id: I0382a279b158fe669951fd28b705d2ab7ce5074d
Review URL: http://codereview.chromium.org/6254002
/external/autotest/client/cros/login.py
|
| 51d1939bf47960b6e65042402a900e0564aa6d3e |
|
06-Jan-2011 |
Eric Li <ericli@google.com> |
Rename cros/ui.py into cros/cros_ui.py, and adjust all other import refereces as needed.
Change-Id: I6f1c28d817f91b979737ea3a4cafa9ea23cc693a
BUG=7236
TEST=
1. run
grep -wnrc ui server/* | grep -v $":0" | sort
grep -wnrc ui client/* | grep -v $":0" | sort
to find out all reference to ui module.
2. emerge autotest, and run bvt against a live system.
Review URL: http://codereview.chromium.org/6037017
/external/autotest/client/cros/login.py
|
| e7c4cab13a8576a4f9de41b2dc1fb8c45c97424c |
|
05-Jan-2011 |
Eric Li <ericli@google.com> |
Change-Id: Ib50962111d0c6c07a135679d80930af4bc52915b
Move site_chrome_test, site_logging, site_log_reader,
site_crash_test into cros dir.
site_chrome_test --> cros/chrome_test
site_crash_test --> cros/crash_test
site_logging --> cros/cros_logging
site_log_reader --> cros/cros_logging
site_ui_test --> cros/cros_ui_test
I had removed site_logging module and moved its code into cros_logging, since its new name (logging) has conflict with python's logging module.
site_log_reader has also been merged into cros_logging module.
As I am touching all the files in the list, I also removed some unnecessary import to autotest_lib.client.bin.test.
Change-Id: I2c8f101a6c7a0499619e227e4cb0cfb8ceec4690
BUG=7236
TEST=run bvt and every other tests been touched from both source (third_party/autotest/files) and chroot (/build/board/usr/local/autotest)
Review URL: http://codereview.chromium.org/5740004
/external/autotest/client/cros/login.py
|
| c4d8f4aab4e434fcb1a9fb33931768ffebfb8f1c |
|
10-Dec-2010 |
Eric Li <ericli@google.com> |
Move site_httpd, site_uim, site_login and site_cryptohome into cros/ dir.
And change import site_utils to import utils as I touched more source code.
Change-Id: I18bbac502c67ddedaccc7ef034c4f8c8b204506e
BUG=7236
TEST=BVT
Review URL: http://codereview.chromium.org/5680003
/external/autotest/client/cros/login.py
|