Update Browser Restart for Pixel Tests
If a GPU Pixel Test crashes during init, it will attempt to close the non existent browser, crashing the run. Once a test ends, it restarts the browser, with the current command line. This leads to command lines propagating between tests. Normally a test will then restart the browser an additional time, with new command line args, if desired. However if init is failing, this then persists for all subsequent tests. This change updates the restart behaviour to detect failed init. Then to use default args for the restart. To allow subsequent tests the change to succeed at init. Furthermore, ChromeBrowserBackend._GetDevToolsClient can timeout while we are attempting to handle exceptions in _RunGpuTest. Leading to the test suite left without an open browser. This error then cascades, leading to the next test to also fail. (crbug.com/993379) This change also updates _EnsureTabIsAvailable to create a browser with the default options if we are ever in such a case. To prevent one failure from affecting subsequent runs. Bug: 985530 Change-Id: I7256fa01e9b1e5d84a65a7073b3fb625a716f13c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715778 Commit-Queue: Jonathan Ross <jonross@chromium.org> Reviewed-by:Brian Sheedy <bsheedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#686566}
Showing
Please register or sign in to comment