Many tests create their own FiberScheduler. These objects do not seem to get reclaimed automatically (at least under OpenJDK 1.8.0), and each FiberScheduler entails at least one Thread. Hence, when testing everything at once, the number of Threads overwhelm the system and more Threads cannot be created, leading to OutOfMemoryErrors and thus test failures. However, the tests themselves would complete without failure if they were executed in isolation.
This fixes this issue by making the tests clean up after themselves.
Many tests create their own FiberScheduler. These objects do not seem to get reclaimed automatically (at least under OpenJDK 1.8.0), and each FiberScheduler entails at least one Thread. Hence, when testing everything at once, the number of Threads overwhelm the system and more Threads cannot be created, leading to OutOfMemoryErrors and thus test failures. However, the tests themselves would complete without failure if they were executed in isolation.
This fixes this issue by making the tests clean up after themselves.