-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-enable ExecutorWebDriver in Chrome #13225
Comments
Looking at wpt-chrome-dev-testharness-6 things start to go wrong like this (rerun locally):
A few things that stand out:
This is a message from ChromeDriver, just prior to The The bigger problem is when we then run the next test (and, indeed, all following tests) we've not restarted the browser (#13013 is vaguely related here), so we just get WebDriverExceptions for the remainder of the tests. |
So I think the underlying problem is that we were raising ERROR instead of INTERNAL-ERROR and therefore not restarting the browser after this happened? |
#13200 enabled it, but this was reverted in #13220.
See wpt-chrome-dev-testharness-5 and wpt-chrome-dev-testharness-6 logs both of which contain a fair number of tracebacks.
https://staging.wpt.fyi/results/?product=chrome@1e7408fcd3&product=chrome@9bc71d422a&diff=true shows a lot of tests vanishing due to these tracebacks. This suggests there is at least one of the following bugs here:
@jgraham pointed out that in many implementations when the content process crashes the WebDriver "execute script" command just returns
null
, and this is indistinguishable fromwd.execute_script("return null")
.The text was updated successfully, but these errors were encountered: