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
It basically happens when you run harvest again after one run through of testing. running it again, like in the case of testing one scenario over and over, you will get this error and have to wait a while before being able to start it up again.
On closer examination, it appears that between 1.9.x and 1.10x there was a change in the LiveServerThread class in django.testcases.py that disables port reuse. (see https://code.djangoproject.com/ticket/27596#comment:7)
I've suggested that this is their issue but they have asked me to get you guys involved to see if there is something that lettuce should be doing to alleviate this problem?
Thanks for any support or suggestions you have
Mike
The text was updated successfully, but these errors were encountered:
MikeHibbert
changed the title
Django 1.10x breaks when LiveServerTestCase is restarted too quickly
Django 1.10x breaks when LiveServerTestCase if restarted too quickly
Dec 14, 2016
Over in the Django code site, I've reported an issue, (https://code.djangoproject.com/ticket/27596) that causes an error that reports as:
socket.error: [Errno 98] Address already in use
It basically happens when you run harvest again after one run through of testing. running it again, like in the case of testing one scenario over and over, you will get this error and have to wait a while before being able to start it up again.
On closer examination, it appears that between 1.9.x and 1.10x there was a change in the LiveServerThread class in django.testcases.py that disables port reuse. (see https://code.djangoproject.com/ticket/27596#comment:7)
I've suggested that this is their issue but they have asked me to get you guys involved to see if there is something that lettuce should be doing to alleviate this problem?
Thanks for any support or suggestions you have
Mike
The text was updated successfully, but these errors were encountered: