Currently, some tests in burn-in mode with InMemory engine can run out of memory (WT_CACHE_FULL error). This can happen even when the test "cleans-up" by deleting the inserted documents and dropping the collection. This is a known problem, but it needs to be solved eventually.

Potential solutions:

• restart the mongod between the test runs when running in burn-in with In-Memory engine
• provide additional JavaScript API for the tests to better clean-up the memory without restarting
• detect the WT_CACHE_FULL error in runCommand() override and fail gracefully without failing the test
• modify the In-Memory burn-in task generator to generate --repeat=1