Mark tests failed with 500 disconnected error as crash (#48059)
- Mark tests failed with 500 disconnected error as crash
In a multiple processes architecture, when the renderer processes
crashed, the liveness check won't necessary fail as the browser process
is still running. One common error we see in Chromium is that webdriver
will report 500 disconnected, with an error message "Unable to receive
message from renderer". Previously the test result is Internal Error
instead of Crash.
Bug: 362506646
- update per comments