#32746: Unexpected test failures in 3.3.2 when running the whole testsuite
-----------------------------------+--------------------------------------
Reporter: Jakub Kulík | Owner: nobody
Type: Bug | Status: closed
Component: Testing framework | Version: 3.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Changes (by Jakub Kulík):
* resolution: needsinfo => invalid
Comment:
I am sorry, I just found the issue and it's entirely on our side.
For posterity: Django test suite can be fragile in a sense that when one
test fails, many unrelated may follow, and that's what happened here.
`test_incorrect_timezone` is the only one that is actually failing and the
cause is our internal Solaris issue with `/usr/share/zoneinfo`. Once
patched, the test suite is again 100% green.
--
Ticket URL: <https://code.djangoproject.com/ticket/32746#comment:6>
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/066.80dc30410f4464301c877f1fbfcd21fe%40djangoproject.com.
