Skip to content
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

Test CL investigating chromedriver timeouts #19609

Closed
wants to merge 23 commits into from
Closed

Test CL investigating chromedriver timeouts #19609

wants to merge 23 commits into from

Conversation

stephenmcgruer
Copy link
Contributor

This is just to give me a PR where I can trigger taskcluster with chrome-dev unpinned and see what debugging I can do.

@wpt-pr-bot wpt-pr-bot added the wptrunner The automated test runner, commonly called through ./wpt run label Oct 10, 2019
@stephenmcgruer
Copy link
Contributor Author

So looks like we get stuck in our self.wait_script (or possibly webdriver has already gone away or something):

do_test for WebDriverRefTestExecutor
Got command: u'log'
RefTestImplementation: run_test. test.references: [(<wptrunner.wpttest.ReftestTest /infrastructure/assumptions/ahem-ref.html>, u'==')]
Got command: u'log'
screenshot: url=http://web-platform.test:8000/infrastructure/assumptions/ahem.html, timeout: 10
Got command: u'log'
_screenshot, executing self.wait_script...
<--- there should be more logs here, based on the CL that ran
Got command: 'test_ended'
Unexpected count in this thread 1
TEST-UNEXPECTED-TIMEOUT | /infrastructure/assumptions/ahem.html | expected PASS

@stephenmcgruer
Copy link
Contributor Author

No longer needed; we got to M79 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci docker infra Taskcluster wpt wptrunner The automated test runner, commonly called through ./wpt run
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants