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

[Gecko Bug 1811545] [wdspec] Enhance stale_element fixture for shadow root nodes. #38208

Merged
merged 5 commits into from
Feb 9, 2023

Conversation

moz-wptsync-bot
Copy link
Collaborator

Differential Revision: https://phabricator.services.mozilla.com/D167542

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1811545
gecko-commit: 55cec0043044a5dca7fa5a2b4108086d6b8f5f17
gecko-reviewers: webdriver-reviewers, jdescottes

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Firefox project.

Differential Revision: https://phabricator.services.mozilla.com/D167542

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1811545
gecko-commit: b1d53199467211157f6324123b4514b568e7bf70
gecko-reviewers: webdriver-reviewers, jdescottes
…est_page fixture.

Differential Revision: https://phabricator.services.mozilla.com/D167543

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1811545
gecko-commit: 46c66c218e3716e6d325f79498449eebbc64dd23
gecko-reviewers: webdriver-reviewers, Sasha, jdescottes
Differential Revision: https://phabricator.services.mozilla.com/D167544

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1811545
gecko-commit: 10f659a585117b5a9bc2e01b2f57c20d81748f11
gecko-reviewers: webdriver-reviewers, Sasha, jdescottes
…and stale / detached state.

Differential Revision: https://phabricator.services.mozilla.com/D167545

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1811545
gecko-commit: d84d48ee0d61a5e119f5f600acb5c16bd8644311
gecko-reviewers: webdriver-reviewers, jdescottes
…ge fixture.

Differential Revision: https://phabricator.services.mozilla.com/D167546

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1811545
gecko-commit: 7724c46f297307a972e338f44521abccc55cdd8d
gecko-reviewers: webdriver-reviewers, jdescottes
@whimboo
Copy link
Contributor

whimboo commented Jan 30, 2023

FYI @sadym-chromium and @foolip for more tests around stale elements and shadow roots.

@whimboo whimboo closed this Jan 30, 2023
@whimboo whimboo reopened this Jan 30, 2023
@jcscottiii jcscottiii closed this Jan 30, 2023
@jcscottiii jcscottiii reopened this Jan 30, 2023
@whimboo
Copy link
Contributor

whimboo commented Jan 31, 2023

@foolip or @nechaev-chromium could one of you please have a look why chromedriver is not able to start Chrome at all for the stability tasks? Thanks.

@nechaev-chromium
Copy link
Contributor

I'm looking into it

@nechaev-chromium
Copy link
Contributor

There are many messages with reading "pthread_create: Resource temporarily unavailable".
It looks like the maximum allowed thread count in the system is exceeded.
This might happen if ChromeDriver crashed and did not close Chrome instances.
I will leave WPT tests running overnight and see if my hypothesis is correct.

@whimboo
Copy link
Contributor

whimboo commented Jan 31, 2023

Ah maybe this is triggered by the additional tests that I added which in some cases causes Chrome to unexpectedly crash the current tab? When inspecting the raw log I can see a lot of the following crashes:

79:42.61 INFO STDOUT: E           webdriver.error.WebDriverException: tab crashed (500): tab crashed
79:42.61 INFO STDOUT: E             (Session info: chrome=111.0.5562.0)
79:42.61 INFO STDOUT: E           

@whimboo
Copy link
Contributor

whimboo commented Jan 31, 2023

And after a couple of those crashes the following is logged and all the remaining tests are failing:

ERROR test_no_top_browsing_context - setup error: webdriver.error.UnknownErrorException: unknown error (500): unknown error: Chrome failed to start: crashed.

Please let me know of your results and if we can safely merge this PR. At least the wpt-chrome-dev-results don't show any issues.

@jcscottiii
Copy link
Contributor

jcscottiii commented Jan 31, 2023

When I try to replicate the CI job locally, I get the same error.

Steps taken locally:

docker run -it webplatformtests/wpt:0.52 bash
# Get a shell into the container.
/home/test/start.sh https://github.com/web-platform-tests/wpt.git refs/pull/38208/merge
cd web-platform-tests
git branch base_head d2e81383796b458968eb86b0dd7033b6a23df05a
git branch pr_head 9cd69f7265cd57fbd5894003242a8ebe8088e757
git fetch --quiet origin master:master
./tools/ci/run_tc.py --ref=refs/pull/38208/merge --head-rev=9cd69f7265cd57fbd5894003242a8ebe8088e757 --merge-rev=170a89d292550698eff44328b85f98e18085aab8 --oom-killer --xvfb --hosts --browser=chrome --channel=dev --install-certificates -- ./tools/ci/taskcluster-run.py --commit-range base_head chrome dev -- --channel=dev --verify --verify-no-chaos-mode --verify-repeat-loop=0 --verify-repeat-restart=10 --github-checks-text-file=/home/test/artifacts/checkrun.md

jcscottiii added a commit that referenced this pull request Jan 31, 2023
@nechaev-chromium
Copy link
Contributor

It does not reproduce locally on my Linux computer with ChromeDriver 112.0.5569.0, Chrome 111.0.5562.0 and WPT (webdriver/tests) from gecko/1811545 branch. There are no abandoned Chrome processes.

@whimboo
Copy link
Contributor

whimboo commented Feb 1, 2023

So maybe it's an issue with the docker image and some installed dependencies? I wonder if you would also be able to reproduce like @jcscottiii is.

@jcscottiii
Copy link
Contributor

I think the failures are unrelated to this PR.

  1. I created [do not merge] debug PR 38208 #38292. This PR has no meaningful changes. Just whitespace. And I see the same error Chrome failed to start: crashed
  2. I also tried this PR locally with chrome stable running ./tools/ci/run_tc.py --ref=refs/pull/38208/merge --head-rev=9cd69f7265cd57fbd5894003242a8ebe8088e757 --merge-rev=170a89d292550698eff44328b85f98e18085aab8 --oom-killer --xvfb --hosts --browser=chrome --channel=stable --install-certificates -- ./tools/ci/taskcluster-run.py --commit-range base_head chrome stable -- --channel=stable --verify --verify-no-chaos-mode --verify-repeat-loop=0 --verify-repeat-restart=10 --github-checks-text-file=/home/test/artifacts/checkrun.md And I get the same error.

cc: @foolip

@whimboo
Copy link
Contributor

whimboo commented Feb 6, 2023

@sadym-chromium your help would be appreciated here so that we can merge this PR. Thanks!

@sadym-chromium
Copy link
Contributor

on it

@sadym-chromium
Copy link
Contributor

I cannot reproduce the Chrome crashes locally. When following the below steps, tests work well (some failures and errors, but no crashes).

When I try to replicate the CI job locally, I get the same error.

Steps taken locally:

docker run -it webplatformtests/wpt:0.52 bash
# Get a shell into the container.
/home/test/start.sh https://github.com/web-platform-tests/wpt.git refs/pull/38208/merge
cd web-platform-tests
git branch base_head d2e81383796b458968eb86b0dd7033b6a23df05a
git branch pr_head 9cd69f7265cd57fbd5894003242a8ebe8088e757
git fetch --quiet origin master:master
./tools/ci/run_tc.py --ref=refs/pull/38208/merge --head-rev=9cd69f7265cd57fbd5894003242a8ebe8088e757 --merge-rev=170a89d292550698eff44328b85f98e18085aab8 --oom-killer --xvfb --hosts --browser=chrome --channel=dev --install-certificates -- ./tools/ci/taskcluster-run.py --commit-range base_head chrome dev -- --channel=dev --verify --verify-no-chaos-mode --verify-repeat-loop=0 --verify-repeat-restart=10 --github-checks-text-file=/home/test/artifacts/checkrun.md

@jgraham
Copy link
Contributor

jgraham commented Feb 9, 2023

Since we think the crashes are unrelated to this PR, I'm going to force-merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants