-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[🐛 Bug]: Tests are just getting queued up though there are available sessions. #2169
Comments
@tv2022, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
Hi @tv2022, in your tests, is there any |
Ok, I missed this statement |
Also, I saw in the steps, |
@VietND96 Thanks for the quick response, don't have any download option enabled in capabilities but I still tried adding it and after few hours I saw this issue again. I also changed Sure I will add this Thanks! |
@VietND96 I can see the issue again with the latest version 4.18.1-20240224 and SE_LOG_LEVEL=FINE. The log file is huge (8GB) so cannot upload the entire file, I am still trying to analyze the log. Do you have any specific inputs or exception to look for related to this issue? I see lot of below exception messages in log.
|
Can you check if there are any logs related to the below string that appeared consecutively in Hub?
|
@VietND96 No, i don't find any exception starting with either first 2 lines.
Also, no log was found with this exception Found the below log related to a few sessions.
|
I don't currently have time to add much detail, but I did want to chime in that I'm seeing the same Edit: |
With the issue, after some time, new requests are not accepted by hub/distributor anymore. If you are deploying Grid in K8s, you can refer to liveness probe settings, it will guard to restart once meet 0 sessions while queue getting up - https://github.com/SeleniumHQ/docker-selenium/tree/trunk/charts/selenium-grid#distributor-probes |
Also, these env vars name looks like not support, mostly it starts with prefix
|
What happened?
Suddenly when we run some automation jobs the grid hub queue size is growing and not allocating sessions though we have enough sessions. We had to restart the grid to overcome this issue. This happens very frequently. We are using podman for configuring our grid. This seems relevant to this issue #1865. Tests will run for some time, and suddenly this issue is popping up.
Capabilities:
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
Operating System
Red Hat Enterprise Linux release 8.9 (Ootpa)
Docker Selenium version (image tag)
4.14.1-20231025
Selenium Grid chart version (chart version)
NA
The text was updated successfully, but these errors were encountered: