cyan-chrome-pfq: VM tests failed for "Timed out waiting for login prompt" |
||||||||
Issue descriptionA bunch of VM tests failed for "Timed out waiting for login prompt" on cyan-chrome-pfq since build 1328. https://uberchromegw.corp.google.com/i/chromeos/builders/cyan-chrome-pfq Suspect something wrong with login web UI related changes. rkc@, do you happen to know any recent web UI login related changes might cause the problem?
,
Jun 29 2017
Until build 1331 all failed for this issue. Then after that build there seems a different error causing VM tests failed.
,
Jun 29 2017
,
Jun 30 2017
,
Jun 30 2017
I didn't really see anything related to web UI changes.
,
Jun 30 2017
There's a huge number of GPU errors in the chrome logs (ie, [1]). I don't think this is login related; I don't see any login-related changes (but I also don't see any GPU related changes). [1478:1651:0627/222028.550416:VERBOSE1:drm_device_handle.cc(83)] Succeeded authenticating /dev/dri/card0 in 0 ms with 1 attempt(s) [1478:1651:0627/222028.687427:ERROR:validation_errors.cc(76)] Invalid message: VALIDATION_ERROR_UNEXPECTED_INVALID_HANDLE (invalid handle or interface ID in array expecting valid handles or interface IDs: array size - 1; index - 0) [1478:1651:0627/222028.687546:ERROR:browser_child_process_host_impl.cc(588)] Terminating child process for bad Mojo message: Received bad user message: Validation failed for GpuService ResponseValidator [VALIDATION_ERROR_UNEXPECTED_INVALID_HANDLE (invalid handle or interface ID in array expecting valid handles or interface IDs: array size - 1; index - 0)] [1478:1651:0627/222028.695960:VERBOSE1:drm_device_handle.cc(83)] Succeeded authenticating /dev/dri/card0 in 0 ms with 1 attempt(s) [1478:1651:0627/222028.797657:ERROR:validation_errors.cc(76)] Invalid message: VALIDATION_ERROR_UNEXPECTED_INVALID_HANDLE (invalid handle or interface ID in array expecting valid handles or interface IDs: array size - 1; index - 0) [1478:1651:0627/222028.797773:ERROR:browser_child_process_host_impl.cc(588)] Terminating child process for bad Mojo message: Received bad user message: Validation failed for GpuService ResponseValidator [VALIDATION_ERROR_UNEXPECTED_INVALID_HANDLE (invalid handle or interface ID in array expecting valid handles or interface IDs: array size - 1; index - 0)] [1478:1651:0627/222028.816562:VERBOSE1:drm_device_handle.cc(83)] Succeeded authenticating /dev/dri/card0 in 0 ms with 1 attempt(s) [1478:1651:0627/222028.967433:ERROR:validation_errors.cc(76)] Invalid message: VALIDATION_ERROR_UNEXPECTED_INVALID_HANDLE (invalid handle or interface ID in array expecting valid handles or interface IDs: array size - 1; index - 0) [1478:1651:0627/222028.967543:ERROR:browser_child_process_host_impl.cc(588)] Terminating child process for bad Mojo message: Received bad user message: Validation failed for GpuService ResponseValidator [VALIDATION_ERROR_UNEXPECTED_INVALID_HANDLE (invalid handle or interface ID in array expecting valid handles or interface IDs: array size - 1; index - 0)] [1478:1651:0627/222028.974615:VERBOSE1:drm_device_handle.cc(83)] Succeeded authenticating /dev/dri/card0 in 0 ms with 1 attempt(s) [1478:1651:0627/222029.098106:ERROR:validation_errors.cc(76)] Invalid message: VALIDATION_ERROR_UNEXPECTED_INVALID_HANDLE (invalid handle or interface ID in array expecting valid handles or interface IDs: array size - 1; index - 0) [1478:1651:0627/222029.098219:ERROR:browser_child_process_host_impl.cc(588)] Terminating child process for bad Mojo message: Received bad user message: Validation failed for GpuService ResponseValidator [VALIDATION_ERROR_UNEXPECTED_INVALID_HANDLE (invalid handle or interface ID in array expecting valid handles or interface IDs: array size - 1; index - 0)] [1]: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/125435306-chromeos-test/chromeos4-row11-rack11-host3/crashinfo.chromeos4-row11-rack11-host3/var/log/chrome/
,
Jun 30 2017
+sadrul@ who has been making mojo GPU changes recently (https://cs.chromium.org/chromium/src/services/ui/gpu/interfaces/?dr=C)
,
Jun 30 2017
,
Jul 1 2017
I think +oshima@ was seeing something locally, which seemed to have resolved itself? Perhaps a clobber build?
,
Jul 1 2017
Oh, this may have been fixed by https://chromium-review.googlesource.com/c/552741/ too.
,
Jan 24 2018
Obsolete. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by jen...@chromium.org
, Jun 29 2017