On Tue, Sep 18, 2012 at 11:23 AM, Jeremy Dunck <jdu...@gmail.com> wrote: ... > And the last one, I hesitate to raise because it's likely to be > specific to my machine, but... our (django-nose-based) test runner > hangs after completing the suite but before tearing down. Using > dtruss I can see it's hanging on select/kevent, and using gdb I see > it's in _mysql_ConnectionObject_query. I'm unsure where to get debug > symbols for either mac python or mysqldb (or at least, I haven't spent > the time to get there). I mention it despite it seeming > environment-specific because it's possibly hanging due to the > unicode/py3 changes. I just don't know. > > #0 0x00007fff9867aaf2 in read () > #1 0x00000001105fe8ba in vio_read () > #2 0x000000011057fbb1 in my_real_read () > #3 0x000000011057f778 in my_net_read () > #4 0x0000000110572cb2 in cli_safe_read () > #5 0x000000011057705d in cli_read_query_result () > #6 0x000000011057608e in mysql_real_query () > #7 0x0000000110563d14 in _mysql_ConnectionObject_query () > #8 0x000000010f738d77 in PyEval_EvalFrameEx ()
Florian and Anssi helped troubleshoot this - https://code.djangoproject.com/ticket/18984 I am using multi-db with some TEST_MIRROR'd aliases, each of which has a pending transaction. The flush at the end of TestCase locks forever waiting for a table lock, essentially deadlocking. Rolling back pending transactions just before flush releases the related locks. I consider this a release blocker because many multidb apps would likely hit this. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
