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
Its not an issue from Selenium extra but its issue from selenium and i am not sure if its already handled by Selenium extra.
we start test over nighwatch and when it goes to error then sessions are taken and not closed till timeout happens, in this case all the sessions are taken from node and node can be accessed anymore and but it does also nothing.
Hi
Its not an issue from Selenium extra but its issue from selenium and i am not sure if its already handled by Selenium extra.
we start test over nighwatch and when it goes to error then sessions are taken and not closed till timeout happens, in this case all the sessions are taken from node and node can be accessed anymore and but it does also nothing.
we can also simulate the same behaviour over http://host/wd/hub/session
is there a way to handle such situation?
Thanks
Chandra
The text was updated successfully, but these errors were encountered: