When running multiple Mir instances in process there's only "emergency_cleanup" for the last to start
Bug #1336750 reported by
Alan Griffiths
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mir |
Triaged
|
Low
|
Unassigned | ||
| mir (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
Bug Description
It probably doesn't happen in many production scenarios but we use multiple Mir servers in (e.g. NestedServer.* tests).
Each Mir config creates an EmergencyCleanup object for that instance and each is saved to namespace scope by run_mir. When running multiple Mir instances in process only the last is saved.
Sharing a single EmergencyCleanu
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #1 |
| Changed in mir: | |
| status: | New → Triaged |
Revision history for this message
| Michał Sawicz (saviq) wrote | #2 |
| Changed in mir (Ubuntu): | |
| importance: | Undecided → Low |
| status: | New → Triaged |
To post a comment you must log in.
Definitely Low. It only affects in-process tests and would never be an issue for real Mir servers.