-
Notifications
You must be signed in to change notification settings - Fork 7
SauceLabs error: The test with session id null has already finished, and can't receive further commands. #32
Comments
Did you get any resolution to this. We are experiencing a similar issue across chrome and firefox |
Hi @DomSkech no, we haven't look into it, yet. Curious, are you experiencing this with a keystone-nightwatch-e2e setup or your own nightwatch setup? |
Our own nightwatch setup. The same suite run perfectly well running locally against the remote test servers. Its only in saucelabs that this issue manifests itself. Interestingly all my tests still appear to 'pass'. Although the logs show the same as you see. If you can eliminate keystone then perhaps we should escalate this to SauceLabs? |
Cool...if you find anything enlightening please share...we'll do the same! |
I'm seeing the same error when running our nightwatch test suite as well. Would be nice if we could get some guidance from SauceLabs on how to further investigate the root cause for this issue. |
Yes we having issues here too :(
|
I am also getting the similar error. But my case it's not parallel execution but sequential only. |
Same error here but mine includes a process id: Failed: The test with session id 0f2b41dc0cd3415c8e84013532f3e464 has already finished, and can't receive further commands. |
It is probably worth logging these errors either with TravisCI or with SauceLabs. It's clear from the amount of people having this problem that it's not really anything to do with Keystone-nightwatch-e2e, and as such nothing is going to be fixed because of this issue... |
For posterity... Similar error, but we get a session id. Occurs on SauceLabs only and does not occur locally. Using protractor and chrome. |
A bit more for posterity... Solved the issue with a combo of sauce config changes:
|
The keystone e2e tests sometimes failed with the following error. Need to figure out why NightwatchJS is not getting notified and/or it is not notifying KNE of any errors.
The text was updated successfully, but these errors were encountered: