Martin noticed that MemoryServer doesn't unregister itself. This adds that to tearDown, and adds some tests for it.
In a quick test, I did see a bunch of MemoryServer registrations left over at the end of the test suite. For example, running all of "per_pack_repository" (300 tests) left about 84 registered memory transports. From what I can tell it doesn't actually leave the MemoryServer in memory, just some functions registered in the transport_list_registry. However, it is hygienic to clean them out.
Martin noticed that MemoryServer doesn't unregister itself. This adds that to tearDown, and adds some tests for it.
In a quick test, I did see a bunch of MemoryServer registrations left over at the end of the test suite. For example, running all of "per_pack_ repository" (300 tests) left about 84 registered memory transports. From what I can tell it doesn't actually leave the MemoryServer in memory, just some functions registered in the transport_ list_registry. However, it is hygienic to clean them out.