Tritcask tests does not always shutdown the instance
Bug #823336 reported by
Natalia Bidart
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu One Client |
Fix Released
|
Medium
|
Natalia Bidart | ||
Bug Description
Or sometimes the instance is shutdown at the end of the tests, so if there is a failure before that, the db is never shutdown.
Related branches
lp:~nataliabidart/ubuntuone-client/tritcask-shutdown
- Roberto Alsina (community): Approve
- Guillermo Gonzalez: Approve
-
Diff: 851 lines (+120/-101)3 files modifiedtests/syncdaemon/test_fsm.py (+20/-20)
tests/syncdaemon/test_tritcask.py (+99/-81)
ubuntuone/syncdaemon/tritcask.py (+1/-0)
| Changed in ubuntuone-client: | |
| assignee: | nobody → Natalia Bidart (nataliabidart) |
| importance: | Undecided → Medium |
| status: | New → In Progress |
| tags: | added: chicharra u1-zomg-windows |
| Changed in ubuntuone-client: | |
| status: | In Progress → Fix Committed |
| Changed in ubuntuone-client: | |
| milestone: | none → 1.7.2 |
| tags: | added: u1-windows |
| Changed in ubuntuone-client: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
