Closed ibodog closed 2 years ago
@ibodog, thank you for creating this issue. We will troubleshoot it as soon as we can.
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.
Thank you!
Can you please share the logs when the Grid starts? Also, how are you starting the Grid? And, please paste in a comment below what you get when going to the /status
endpoint at the Hub and the Windows Node.
I upgraded my local machine to Windows 11 and I see the same. After searching for some minutes, this seems to be a bug in Windows 11, reporting itself as Windows 10. We can wait a while until this is addressed in a future Windows 11 update.
https://docs.microsoft.com/en-us/answers/questions/711686/win11-machine-is-still-showing-windows-10-as-produ.html https://techcommunity.microsoft.com/t5/report-an-issue/os-name-is-shown-as-windows-10-instead-of-windows-11/m-p/2818449
A workaround is to create a custom driver config where you can define the platformName
so the Node shows itself as Windows 11.
https://www.selenium.dev/documentation/grid/configuration/toml_options/#configuring-and-customising-drivers
Is there a reference for the valid keys in the toml file for [node]. Getting error on 'platformName' or 'platform-name' or 'platform'.
[node] detect-drivers = true max-sessions = 8 hub = "http://mygrid.net:4444" platform = Windows 11
It was easier to override "os.name" system property at start of the node (I'm starting from Task Scheduler...). That way you can skip adding the detailed custom driver config.
Something like: "C:\Program Files\Java\jdk-11.0.12\bin\java.exe" -Dos.name="Windows 11" -jar selenium-server-4.1.4.jar node --config node-config.toml
OR just upgrade the JDK to a version where Windows 11 detection via os.name is fixed. 11.0.13 or newer...
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
What happened?
With 4.1.4 update hub and nodes were updated. Test run specifies a platformName of "win11" and the hub cannot find a suitable node to run the test. Checking the info about the node in the Selenium Grid UI the node is incorrectly identified as "Windows 10".
The session appears on the queue as:
{"acceptInsecureCerts":true,"acceptSslCerts":true,"browserName":"chrome","build":"master","goog:chromeOptions":{"args":[],"excludeSwitches":["enable-automation"],"extensions":[]},"name":"alfresco_TestAddSharedFolder.createFolder","pageLoadStrategy":"eager","platformName":"windows 11","screenResolution":"1272x1024","se.screenResolution":"1272x1024","se:recordVideo":true,"se:timeZone":"America/Chicago","tz":"America/Chicago"}
I thought this might be fixed with the platform enum changes in v4.1.4 that support win11 as platformName.
How can we reproduce the issue?
Relevant log output
Operating System
hub (docker-linux), node Windows 11
Selenium version
4.1.4
What are the browser(s) and version(s) where you see this issue?
chrome was tested only
What are the browser driver(s) and version(s) where you see this issue?
using grid
Are you using Selenium Grid?
4.1.4