Changes between Version 2 and Version 3 of Ticket #24080, comment 40
- Timestamp:
- Oct 26, 2015, 3:45:33 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #24080, comment 40
v2 v3 1 This is affecting us also, randomly dying during our automated tests. It is entirely repeatable, but unpredictable where it will break. It happens both locally on our Macs (sqlite v3.7.13) and on Linux. Upgrading to sqlite 3.8 just makes it worse. It happens between tests, where Django tries to rollback the test transaction . The only reliable solution is to stop using Django's TestCase class and instead use the one from unittest, manually deleting in tearDown() any models that the test creates.1 This is affecting us also, randomly dying during our automated tests. It is entirely repeatable, but unpredictable where it will break. It happens both locally on our Macs (sqlite v3.7.13) and on Linux. Upgrading to sqlite 3.8 just makes it worse. It happens between tests, where Django tries to rollback the test transaction in _rollback_atomics. The only reliable solution is to stop using Django's TestCase class and instead use the one from unittest, manually deleting in tearDown() any models that the test creates.