Unfortunately, adding the super() calls didn't help.
On Tuesday, July 14, 2015 at 12:47:02 PM UTC+1, Tim Graham wrote:
>
> Please try adding the super() calls.
>
> On Tuesday, July 14, 2015 at 5:44:09 AM UTC-4, tom.sz...@eporta.com wrote:
>>
>> Hi, yes. Some of my test classes do use setUpClass()
Hi, yes. Some of my test classes do use setUpClass() without calling
super().
On Monday, July 13, 2015 at 5:44:03 PM UTC+1, Tim Graham wrote:
>
> Do your test classes use setUpClass() and/or tearDownClass()? If so, are
> you missing super() calls in those methods?
>
> On Monday, July 13, 2015 at
Thanks for the link.
This is the commit at which my tests start failing:
da9fe5c Fixed #20392 -- Added TestCase.setUpTestData()
On Monday, July 13, 2015 at 12:39:57 PM UTC+1, Tim Graham wrote:
>
> That's a starting point, but there are still a lot of commits between 1.8
> and 1.7.x. Here's what I
Thanks for the swift reply. The problem starts with Django 1.8.0. My test
suite passes on all 1.7.x versions.
On Friday, July 10, 2015 at 2:32:25 PM UTC+1, Tim Graham wrote:
>
> No ideas, but if you could bisect to find the Django commit where the
> problem started to appear that will probably h
Hi,
I've recently tried upgrading from Django 1.7.6 to 1.8.3 but haven't been
able to get my test suite to pass.
My main problem is that all of the tests pass when run individually, but
when run as an entire test suite, many arbitraily fail due to an
*InterfaceError:
connection already closed
5 matches
Mail list logo
