#33855 closed Bug (fixed)
System check calls are unnecessary in test worker initialization.
Reported by: | Mariusz Felisiak | Owned by: | Mariusz Felisiak |
---|---|---|---|
Component: | Testing framework | Version: | 4.1 |
Severity: | Release blocker | Keywords: | |
Cc: | David Smith, Nick Pope, Carlton Gibson | Triage Stage: | Ready for checkin |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
3b3f38b3b09b0f2373e51406ecb8c9c45d36aebc added calling system checks to initialization of each test worker. I don't see any reason to do this, it slows down tests (check
is called with all databases
for each alias and once more in DiscoverRunner.run_tests()
) and can cause crashes as some checks require database access.
It seems that it was added to satisfy check_framework.tests.ChecksRunDuringTests.test_registered_check_did_run
on spawn
. IMO we can skip this test on spawn
.
Change History (6)
comment:1 by , 2 years ago
comment:3 by , 2 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:4 by , 2 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
Note:
See TracTickets
for help on using tickets.
This also partly explains why tests on MySQL have become so slow.