#21222: ./runtests.py with two Postgress databases hangs infinitly. Did I just
discover a 1.6 release blocker, or am I doing something wrong?
-------------------------------------+-------------------------------------
     Reporter:  vernondcole          |                    Owner:  nobody
         Type:  Uncategorized        |                   Status:  new
    Component:  Uncategorized        |                  Version:  master
     Severity:  Release blocker      |               Resolution:
     Keywords:  runtests infinite    |             Triage Stage:
  wait                               |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by akaariai):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 You have two connections to the same DB, and for that reason you are
 likely ending up in some sort of deadlock. Maybe having more than one
 connection to the same DB shouldn't validate, but other than that this
 doesn't seem like a bug at all.

 Can you confirm that changing the 'other' alias to use different database
 (different NAME) fixes the issue?

-- 
Ticket URL: <https://code.djangoproject.com/ticket/21222#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.47095c047c5c459f73d2ea123549b703%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to