I've been attempting to write some end to end integration tests using selenium for my current django app (ver 1.3), and have been having a problem with the login function hanging. After much tracing, I have discovered it hangs when psycopg2 (ver 2.4) tries to execute the update query for the last login. I have tested this, and it appears to be running into a database lock on this record, but only when it is run from an instance of django.test.TestCase. I cannot repeat this when using a stand alone script.
I have tried with both runserver and gunicorn, and both have shown the same issue. Using gunicorn with multiple workers to make sure both should operate simultaneously, I started a stand alone copy of the selenium calls to the test server while the TestCase was running. It got to the point of the update, hung until the test timed out, and then completed successfully. I am completely at a loss on how to work around this and was wondering if anyone has seen this problem before or has any ideas on how to attack it? Thanks, Dave -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
