New issue
Advanced search Search tips

Issue 899076 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Improve error diagnostics when trying to run client autotests with virtual terminal open on device

Project Member Reported by cjmcdonald@chromium.org, Oct 25

Issue description

`test_that ${DUT_IP} video_PlaybackPerf.vp9` fails with timeouts or other errors when virtual terminal is open on DUT but succeeds when on OOBE screen

test errors seen:
---------------------------------------------------------------------------------------------
/tmp/test_that_results_pIyoVs/results-1-video_PlaybackPerf.vp9                    [  FAILED  ]
/tmp/test_that_results_pIyoVs/results-1-video_PlaybackPerf.vp9                      FAIL: Unhandled BrowserConnectionGoneException: Timed out while waiting 240s for _GetDevToolsClient.
/tmp/test_that_results_pIyoVs/results-1-video_PlaybackPerf.vp9/video_PlaybackPerf [  FAILED  ]
/tmp/test_that_results_pIyoVs/results-1-video_PlaybackPerf.vp9/video_PlaybackPerf   FAIL: Unhandled BrowserConnectionGoneException: Timed out while waiting 240s for _GetDevToolsClient.
/tmp/test_that_results_pIyoVs/results-1-video_PlaybackPerf.vp9/video_PlaybackPerf   10/25 15:36:10.111 ERROR|           browser:0054| Failed with BrowserConnectionGoneException while starting the browser backend.
---------------------------------------------------------------------------------------------

---------------------------------------------------------------------------------------------
/tmp/test_that_results_JEw2ba/results-1-video_PlaybackPerf.vp9                    [  FAILED  ]
/tmp/test_that_results_JEw2ba/results-1-video_PlaybackPerf.vp9                      FAIL: Unhandled DevToolsClientConnectionError: ''
/tmp/test_that_results_JEw2ba/results-1-video_PlaybackPerf.vp9/video_PlaybackPerf [  FAILED  ]
/tmp/test_that_results_JEw2ba/results-1-video_PlaybackPerf.vp9/video_PlaybackPerf   FAIL: Unhandled AssertionError: sh: 0: getcwd() failed: No such file or directory
---------------------------------------------------------------------------------------------


To reproduce:
1. power on DUT and switch to virtual terminal 2
2. run `test_that ${DUT_IP} video_PlaybackPerf.vp9` on workstation





 
Status: WontFix (was: Untriaged)
I think this is WAI or not planned to fix
Labels: -Type-Bug Type-Feature
Status: Untriaged (was: WontFix)
Summary: client autotests fail with confusing error message when virtual terminal open on device (was: client autotests fail when virtual terminal open on device)
The behavior being WontFix is fine but the error generated was very confusing. I'll change this to a feature request for a better error message.
Summary: Improve error diagnostics when trying to run client autotests with virtual terminal open on device (was: client autotests fail with confusing error message when virtual terminal open on device)

Sign in to add a comment