#27160: Document that running the Django test suite requires creating the 
databases
and, on PostgresQL, a superuser
--------------------------------------+------------------------------------
     Reporter:  pacahon               |                    Owner:  nobody
         Type:  Cleanup/optimization  |                   Status:  new
    Component:  Documentation         |                  Version:  1.9
     Severity:  Normal                |               Resolution:
     Keywords:                        |             Triage Stage:  Accepted
    Has patch:  0                     |      Needs documentation:  0
  Needs tests:  0                     |  Patch needs improvement:  0
Easy pickings:  0                     |                    UI/UX:  0
--------------------------------------+------------------------------------

Comment (by pacahon):

 Replying to [comment:2 cjerdonek]:
 >  Django system tests freezes on my machine with default settings
 (sqlite)
 >
 > Can you say more about this, like what OS you are using and what you
 mean when you say the tests "freeze" (e.g. what is happening exactly)?
 I'm wondering if it's related to ticket #27086 that I filed recently. It
 seems like the freezing is the more fundamental problem, since that
 shouldn't be happening in the first place, right?

 OS X 10.10.5, python 3.4.3 under venv, stable/1.9.x branch

 With `python tests/runtests.py --parallel=1 -v3 admin_views` I get
 `Segmentation Fault 11`:

 {{{
 ...
 test_named_group_field_choices_filter
 (admin_views.tests.AdminViewBasicTest) ... ok
 test_popup_add_POST (admin_views.tests.AdminViewBasicTest) ... ok
 test_popup_dismiss_related (admin_views.tests.AdminViewBasicTest) ... ok
 Segmentation fault: 11
 }}}
 Don't know what the next testcase, no output name for it.

 Without `--parallel=1` it suddenly hang on different testcases
 {{{
 # python tests/runtests.py  -v3
 test_default_and_given_options
 (test_runner.tests.CustomTestRunnerOptionsTests) ... ok
 test_default_options (test_runner.tests.CustomTestRunnerOptionsTests) ...
 ok
 test_option_name_and_value_separated
 (test_runner.tests.CustomTestRunnerOptionsTests) ... ok
 test_output_normal (test_runner.test_debug_sql.TestDebugSQL) ... ok
 test_output_verbose (test_runner.test_debug_sql.TestDebugSQL) ... ok
 # hang, zero CPU activity on each child process
 }}}

 {{{
 # python tests/runtests.py  -v3 admin_views
 test_user_fk_delete_popup (admin_views.tests.UserAdminTest)
 User deletion through a FK popup should return the appropriate JavaScript
 response. ... ok
 test_user_permission_performance (admin_views.tests.UserAdminTest) ... ok
 # the same, hang with 0 CPU activity
 }}}

 I guess we should continue in #27086?

--
Ticket URL: <https://code.djangoproject.com/ticket/27160#comment:3>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.a68e303a31d2956e75d333aac815c50a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to