You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We run selenium in github actions, when not killing the process properly, github action has problems of getting rid ot the test runner, leading to a timeout. driver.quit do not kill the process like it is needed (see #10795).
This issue is handled with the PR #10796 which removes the functions getDefaultService and setDefaultService. Unfortunally this PR includes breaking changes and made it into version ^4.
Previously the functions where used like this when starting a service:
@MarkusJLechner, thank you for creating this issue. We will troubleshoot it as soon as we can.
Info for maintainers
Triage this issue by using labels.
If information is missing, add a helpful comment and then I-issue-template label.
If the issue is a question, add the I-question label.
If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable G-* label, and it will provide the correct link and auto-close the
issue.
After troubleshooting the issue, please add the R-awaiting answer label.
What happened?
We run selenium in github actions, when not killing the process properly, github action has problems of getting rid ot the test runner, leading to a timeout.
driver.quit
do not kill the process like it is needed (see #10795).This issue is handled with the PR #10796 which removes the functions
getDefaultService
andsetDefaultService
. Unfortunally this PR includes breaking changes and made it into version ^4.Previously the functions where used like this when starting a service:
We use mocha as a test runner (
yarn test
triggers it), which will opens a chrome browser in the before hook.In github actions under Complete job this will be logged:
How can we reproduce the issue?
A github action runner running selenium 4.3.1.
Inside
yarn test
we simply use mocha to start the browser and close/quit it.Operating System
Ubuntu latest
Selenium version
4.3.1
What are the browser(s) and version(s) where you see this issue?
Chrome 99
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver 99
Are you using Selenium Grid?
No response
The text was updated successfully, but these errors were encountered: