I run parallel automated tests against selenium mesh.
Sometimes the test fails with;
Session [c1d99cc1-c689-4053-b68d-51c3682c13c4] was terminated due to CLIENT_STOPPED_SESSION (org.openqa.grid.common.exception.GridException) [remote server] org.openqa.grid.internal.ActiveTestSessions(ActiveTestSessions.java):105:in `getExistingSession'
Selenium documentation says:
CLIENT_STOPPED_SESSION The session was stopped using an ordinary call to stop/quit on the client. Why are you using it again??
However, I know that the client did not try to stop / close. I use parallel rspec, so each thread is actually its own Ruby instance, so there is no testing problem.
Also, if I directly request Node using http: // {node_ip}: 5556 / wd / hub / static / resource / hub.html, I see that the session is still open. If quit / stop was issued, this session would be deleted.
It seems that only the session registry in the Selenium Grid Hub considers this session to be stopped. There is no evidence that the session is being stopped elsewhere.
Is there a known grid issue where an invalid session is marked as stopped?
source share