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

Better handle stuck WebDriver processes #4350

Merged
merged 1 commit into from
Dec 15, 2024

Conversation

daxpedda
Copy link
Collaborator

@daxpedda daxpedda commented Dec 10, 2024

The first problem with Safari was that it could simply fail to bind the port, in which case we should keep re-trying. This was addressed in #4320.

However there is a second problem: sometimes MacOS decides that the WebDriver doesn't have permissions. In which case the process gets stuck and we never figure out that it failed and therefor also don't retry.

This PR adds an additional detection mechanism where it reads the Stderr output, if something is in there when we just started, it means that the WebDriver failed to start and we just kill it and try again.

Inspired by flutter/engine#48791.

@daxpedda daxpedda marked this pull request as draft December 10, 2024 23:09
@daxpedda daxpedda force-pushed the safari-webdriver branch 3 times, most recently from e0827d8 to e1032f3 Compare December 11, 2024 00:09
@daxpedda daxpedda marked this pull request as ready for review December 11, 2024 00:18
@daxpedda daxpedda merged commit 37f0aa1 into rustwasm:main Dec 15, 2024
67 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant