#27316: Multiple LiveServerTestCase subclasses cannot reuse the same port
-----------------------------------+--------------------------------------
Reporter: Jeremy Bowman | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Comment (by Jeremy Bowman):
The auto-binding to port 0 does seem to fix the immediate problem (because
it ignores the setting that was restricting it to a single specified
port). I certainly hope that the OS would free up the already used ports
before it started running out of available ones, so I don't expect much of
a problem there. The last problem would be the inability to script the
test to use a known port so other code can also interact with it; I
vaguely remember having a use case for that before (something something
running Selenium in a Docker container), but it's probably a bad thing to
be depending on anyway. And it might have been just the IP address I
needed, not the port.
So yeah, it looks like this may be fixed for the next major release, and
would just be an issue for 1.10.x.
--
Ticket URL: <https://code.djangoproject.com/ticket/27316#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.0c86cd82c8d48f977fd248c24025a505%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
