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
I tracked it down to here, where the command is returning pid 4961 SIGKILL (signal 9) on the status on line 67, causing line 79 to eventually cause the process to die.
This randomly started happening to me earlier today, and eventually 4 other members of my team started experiencing this as well. I don't have a ton of knowledge on how Selenium Manager works, but due to the random nature of this I imagine some process on my machine is pulling in some updated version of the bin/macos/seneium-manager executable and that is causing problems, but that's just my best guess.
@kevin-roe, 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?
When running tests today Selenium started failing with this message:
I was able to reproduce the issue with this simple code:
I tracked it down to here, where the command is returning
pid 4961 SIGKILL (signal 9)
on thestatus
on line 67, causing line 79 to eventually cause the process to die.This randomly started happening to me earlier today, and eventually 4 other members of my team started experiencing this as well. I don't have a ton of knowledge on how Selenium Manager works, but due to the random nature of this I imagine some process on my machine is pulling in some updated version of the
bin/macos/seneium-manager
executable and that is causing problems, but that's just my best guess.How can we reproduce the issue?
Operating System
MacOS Sequoia
Selenium version
Ruby 4.25.0
What are the browser(s) and version(s) where you see this issue?
Chrome 130.0.6723.59, Firefox 131.0.3
What are the browser driver(s) and version(s) where you see this issue?
Can't get the driver - that is the problem
Are you using Selenium Grid?
No
The text was updated successfully, but these errors were encountered: