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

Test execution issue: for "shared" test contexts in multithreading [SPR-8942] #13582

Closed
spring-issuemaster opened this Issue Dec 17, 2011 · 1 comment

Comments

Projects
None yet
2 participants
@spring-issuemaster
Copy link
Collaborator

spring-issuemaster commented Dec 17, 2011

Alexey Semenov opened SPR-8942 and commented

There are several db aware tests.

  1. *mvn* test -Dtest.thread.count=*1* - tests always passed
  2. *mvn* test -Dtest.thread.count=*10* - tests sometimes failed (running tests in several threads)
  3. *mvn* test -Dtest.thread.count=*10* -Pex - tests always passed (running tests in several threads, test with "inherited test context" in excluded from execution)

@DirtiesContext didn't help.
Most common reason of a test failure is inability to load entity just saved.
Reproducible for both: AbstractTestNGSpringContextTests and AbstractTransactionalTestNGSpringContextTests.
It looks like there is an issue in context loading/caching/sharing mechanism in case of multithreading execution.

Reproducible only from command line (not IDE).
spring versions: all (2.5.6 - 3.1.0.M2)
testng versions: all (5.* - 6.*)
hibernate versions: all (3.* - 4.0.0.Final)
maven versions: 2., 3.

p.s. the issue is same as #11897


Affects: 3.0.3, 3.0.4, 3.0.5, 3.0.6

Attachments:

Issue Links:

  • #10532 Allow for concurrent test execution in the TestContext framework

2 votes, 3 watchers

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator

spring-issuemaster commented Sep 3, 2016

Sam Brannen commented

Alexey Semenov,

I downloaded the attached ZIP file and ran the tests using Maven from the command-line; however, I was never able to reproduce the error.

I am therefore closing this issue; however, if you can reproduce this problem against Spring Framework 4.2, 4.3, or 5.0 (milestones), please let us know.

Thanks!

Sam

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment