[GEODE-1402] checkOrphans should not be called in tearDown

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0-incubating.M3
• Component/s: offheap
• Assignee: Darrel Schneider
• Reporter: Darrel Schneider
• Created: 17/May/16 00:07
• Updated: 22/Aug/16 16:55
• Resolved: 17/May/16 16:55

Description

Some unit tests currently call checkOrphans in tearDown. The problem with doing this is if checkOrphans detects an orphan it will throw an exception. This will cause other tearDown tasks to not be done which can cause later unit tests to fail because the previous test did not get to clean everything up.