| Issue 203325: | login_CryptohomeUnmounted test fails, tree closer | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
Chrome OS Version : 0.16.1014.0 Chrome Version : <From about:version: Google Chrome x.x.x.x> Type of computer : x86-alex-binary login_CryptohomeUnmounted is failing. Sometimes it times out trying to login (as shown below) and sometimes (0.16.1015.0) the entire VMTest stage of the build fails with a time out. I suspect a chrome crash or a problem with chrome, not a bug in the cryptohome software. http://chromeosbuild9.mtv.corp.google.com/archive/x86-alex-private-bin/0.16.1014.0-a1-b1232/test_results.tgz Look for testUpdateKeepStateful/2_verify/suite_Smoke/job_report.html STATUS: START login_CryptohomeUnmounted login_CryptohomeUnmounted timestamp=1315569155 localtime=Sep 09 04:52:35 ERROR login_CryptohomeUnmounted login_CryptohomeUnmounted timestamp=1315569210 localtime=Sep 09 04:53:30 Error during login (performancetestaccount@gmail.com, perfsmurf): Login timed out. Please try again.. END ERROR login_CryptohomeUnmounted login_CryptohomeUnmounted timestamp=1315569210 localtime=Sep 09 04:53:30 DMESG: File not found. What is the expected output? What do you see instead? How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) What is the impact to the user, and is there a workaround? If so, what is it? Please provide any additional information below.
Mar 16, 2013
#1
bugdroid1@chromium.org
Mergedinto:
chromium-os:19200
Sep 9, 2011
This seems to have magically resolved itself. http://chromeos-botmaster.mtv.corp.google.com:8026/builders/x86-alex-binary/builds/1234 This is not a good outcome. Some time should be spent trying to understand why the test is flaky -- but I suspect it is related to Chrome instability. The failure is a failure to login.
Sep 9, 2011
David James: just checked, alex binary is the lack of RAM issue because it had parallel test timeout Jason Glasgow: How should I know that? Are all timeouts lack of RAM? David James: yes if they occur on that bot crostestutils.lib.parallel_test_job.ParallelJobTimeoutError: Exceeded max time of 2400 seconds to wait for job completion. only that bot has a shortage of RAM scottz said he'd fix today
Status:
Invalid
Sep 9, 2011
(No comment was entered for this change.)
Status:
Duplicate
Mergedinto: 19200
Mar 6, 2013
(No comment was entered for this change.)
Labels:
OS-Chrome
Mar 9, 2013
(No comment was entered for this change.)
Labels:
-TreeCloser Hotlist-TreeCloser
|
||||||||||||||
| ► Sign in to add a comment | |||||||||||||||