Method DbTestCase.heavy_init() gets called more than once if we run tests via tox
Bug #1413535 reported by
Renat Akhmerov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mistral |
Triaged
|
Medium
|
Nikolay Makhotkin | ||
Bug Description
For some reason "heavy_init" is called more than once if we run tests using tox. For that reason sometimes we get a DB deadlock (also confirmed for MySql). The assumption is that it happens with transactions that delete all actions and add all actions into DB.
| Changed in mistral: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Nikolay Makhotkin (nmakhotkin) |
| milestone: | none → kilo-2 |
Revision history for this message
| Dmitri Zimine (i-dz) wrote | #1 |
| Changed in mistral: | |
| milestone: | kilo-2 → kilo-3 |
| no longer affects: | mistral/kilo |
| no longer affects: | mistral/liberty |
| no longer affects: | mistral/mitaka |
| Changed in mistral: | |
| status: | New → Triaged |
To post a comment you must log in.
This gist has a stack trace of failures when Mistral tests run with MySQL backend, with and without concurrency.
https:/