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
* fix: restarted browsers not running tests
Currently whenever a browser disconnects completely (no socket.io connection loss), the launcher is instructed to "restart" the browser. Whenever the restarted browser now tries to "register" again, Karma considers the browser instance to be still executing and doesn't do anything about it (except setting the state to `EXECUTING` again).
This means that the browser is in the state of executing, but
practically it does nothing just waits. Resulting another disconnect
(repeat here).
* test: add unit test that covers disconnected restarted browsers
* fixup! test: add unit test that covers disconnected restarted browsers
Address feedback
* fixup! test: add unit test that covers disconnected restarted browsers
Improve comments & log messages
constCONNECTED='CONNECTED'// The browser is connected but not yet been commanded to execute tests.
8
8
constCONFIGURING='CONFIGURING'// The browser has been told to execute tests; it is configuring before tests execution.
9
9
constEXECUTING='EXECUTING'// The browser is executing the tests.
10
-
constEXECUTING_DISCONNECTED='EXECUTING_DISCONNECTED'// The browser is executing the tests, but temporarily disconnect (waiting for reconnecting).
11
-
constDISCONNECTED='DISCONNECTED'// The browser got permanently disconnected (being removed from the collection and destroyed).
10
+
constEXECUTING_DISCONNECTED='EXECUTING_DISCONNECTED'// The browser is executing the tests, but temporarily disconnect (waiting for socket reconnecting).
11
+
constDISCONNECTED='DISCONNECTED'// The browser got completely disconnected (e.g. browser crash) and can be only restored with a restart of execution.
0 commit comments