Changes between Initial Version and Version 1 of Ticket #27316, comment 7


Ignore:
Timestamp:
Mar 7, 2017, 3:14:47 PM (8 years ago)
Author:
David Muller

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #27316, comment 7

    initial v1  
    11Hello, thanks for reporting this bug Jeremy.  We are trying to upgrade from Django 1.9.12 to Django 1.10.6 and having the same problem that Jeremy described -- each LiveServerTestCase seems to require a brand new port. 
    22
    3 More concretely, our ability to specify one (and only) one live server address via the `--liveserver` option (e.g. `python manage.py test --liveserver=localhost:8000`) is now broken -- as soon as we try to instantiate our second LiveServerTestCase subclass we get an address already in use error.
     3More concretely, our ability to specify one (and only one) live server address via the `--liveserver` option (e.g. `python manage.py test --liveserver=localhost:8000`) is now broken -- as soon as we try to instantiate our second LiveServerTestCase subclass we get an address already in use error.
    44
    55> Marking as "fixed" in the sense that the issue is fixed in 1.11.
Back to Top