Unclosed test utilities cause leaking of threads

Description

The tests using RamIndexManager.makeRamDirectory() directly should also make sure to close the produced IndexManager, or this keeps hold on worker threads.

While at it, we might want to rename the method as it's build an IndexManager and no longer a Directory.

Activity

Show:
Fixed

Details

Assignee

Reporter

Components

Sprint

Fix versions

Priority

Created May 19, 2016 at 1:29 PM
Updated September 5, 2016 at 6:42 PM
Resolved August 24, 2016 at 3:33 PM