#31117: ThreadTests fails due to double test_ prefix caused by 
TestDbCreationTests.
-----------------------------------+------------------------------------
     Reporter:  Matthijs Kooijman  |                    Owner:  nobody
         Type:  Bug                |                   Status:  new
    Component:  Testing framework  |                  Version:  master
     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 Matthijs Kooijman):

 Turns out the problem with restoration of settings also exists in
 `backends.sqlite.test_creation`. This was not previously a problem because
 `backends.base.test_creation.TestDbCreationTests` would sever the
 reference between `connection.settings_dict` and
 `connections.databases['default']`, but with that fixed, this problem is
 not exposed in the sqlite tests. I've added a fix for this in the PR as
 well.

    No, but it doesn't contain anything unusual. Jenkins runs the entire
 test suite without a parallel flag, that's why it works. For example

 This does not seem true after all. Further investigation (using some dummy
 commits to trigger Jenkins builds with extra debug output) shows that
 Jenkins puts `DJANGO_TEST_PROCESSES=1` in the environment, which limits
 the build to a single process, so that cannot be the culprit here. I've
 been doing some experiments in https://github.com/django/django/pull/12248
 to figure out why Jenkins does not have this problem, but I'm having some
 problems getting the right debug output from Jenkins. I'll update here
 when I figure out something definitive.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31117#comment:4>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/074.279926f29e2b5784cb745ae3f1b2b541%40djangoproject.com.

Reply via email to