#29187: test_delete_signals occasionally fails when running all django tests
-------------------------------------+-------------------------------------
Reporter: Jacob Mulford | Owner: Jacob
| Walls
Type: Bug | Status: closed
Component: Core (Other) | Version: 2.0
Severity: Normal | Resolution: fixed
Keywords: tests, unit tests | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"15bcbeeb95ca34385c119acea14df1f5e7274d45" 15bcbee]:
{{{#!CommitTicketReference repository=""
revision="15bcbeeb95ca34385c119acea14df1f5e7274d45"
Fixed #29187 -- Fixed flaky receiver count assertion in signals tests.
Signal.receivers prunes dead weak references lazily, so a weak receiver
garbage-collected elsewhere could still occupy a slot when
BaseSignalSetup.setUp() counted receivers. The test's own
connect/send/disconnect calls would then prune before tearDown()
counted again.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29187#comment:9>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019eb33f5edb-3b333625-ed75-4c8c-a4f1-6676ca54ab76-000000%40eu-central-1.amazonses.com.
