Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ISPN-9863 Fix leak-related random failures #6724

Merged
merged 1 commit into from Mar 5, 2019

Conversation

danberindei
Copy link
Member

Update for ISPN-9863 because it wasn't always catching leaks in the spring5 modules, depending on whether the last test to run called TestResourceTracker or not.

  • Don't require tests to extend AbstractInfinispanTest
  • TestNG modules check for thread leaks by running ThreadLeakCheckTest
    from the commons-test module
  • JUnit modules check for thread leaks explicitly
    or in JUnitTestListener

@danberindei danberindei force-pushed the ISPN-9863_redo branch 4 times, most recently from 1f10542 to 7fc06a1 Compare March 1, 2019 07:50
@danberindei danberindei changed the title [preview] ISPN-9863 Fix leak-related random failures ISPN-9863 Fix leak-related random failures Mar 1, 2019
@danberindei
Copy link
Member Author

Ready for review, random failures in JCacheConfigurationTest are caused by https://issues.jboss.org/browse/ISPN-9917

@danberindei danberindei force-pushed the ISPN-9863_redo branch 2 times, most recently from 7cfbb54 to 310f156 Compare March 1, 2019 08:28
* Move leak detection to a @AfterSuite configuration method.
  That way leak detection works even if the last test does not
  extend AbstractInfinispanTest.
* Also move detection of wrong/missing groups or testName
  to a @BeforeSuite method + fix LimitExpiryFactoryTest.
* TestNG modules run ThreadLeakCheckTest from commons-test.
* JUnit modules check for thread leaks in JUnitTestListener
  and/or TestResourceTrackingListener.
* JUnitTestListener.testRunFinished failures still build, so tests that
  may leak threads should use TestResourceTrackingListener.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants