#32746: Unexpected test failures in 3.3.2 when running the whole testsuite
---------------------------------------------+------------------------
Reporter: Jakub KulĂk | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 3.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
---------------------------------------------+------------------------
We recently introduced Django 3.3.2 to Solaris (with Python 3.9) and we
are hitting unexpected test failures when running the full test suite on
SPARC. When I rerun those tests one by one however, they are successful.
My guess is that parts of the test suite are not independent and affect
each other.
Errors we are seeing are (although I am not sure that they are always the
same and they changed since 3.3.1):
{{{
ERROR: test_output_normal (test_runner.test_debug_sql.TestDebugSQL)
ERROR: test_output_verbose (test_runner.test_debug_sql.TestDebugSQL)
ERROR: test_setupclass_exception (test_runner.test_debug_sql.TestDebugSQL)
ERROR: test_lazy_base_url_init (file_storage.tests.FileSystemStorageTests)
FAIL: test_incorrect_timezone (settings_tests.tests.SettingsTests)
FAILED (failures=1, errors=4, skipped=1146, expected failures=4)
}}}
Running the test suite with `--reverse` results in many more failures
(attached).
This happens on SPARC only, Intel test results are clean (both with and
without `--reverse`). Our other Django 2.2.21 with Python 3.7 is clean as
well on both platforms.
I am not sure how to continue/investigate the issue further, but I am
happy to do so if guided a little.
I have yet to try Django 3.1 or Python 3.7 (but runtime is highly unlike
the problem).
--
Ticket URL: <https://code.djangoproject.com/ticket/32746>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/051.415e36da2713ec2ff41662e57642cd45%40djangoproject.com.