Add Test-case for lazy DS-Component activation deadlock (issue #15) #31
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
HannesWell
force-pushed
the
deadLockTestCase
branch
from
7a40882 to
331931a
Compare
HannesWell
force-pushed
the
deadLockTestCase
branch
from
331931a to
b0d9a45
Compare
|
I think the new tests should be moved to |
HannesWell
force-pushed
the
deadLockTestCase
branch
from
b0d9a45 to
7718aaf
Compare
HannesWell
force-pushed
the
deadLockTestCase
branch
from
7718aaf to
ab4a81c
Compare
|
Integrated into #68 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was originally created as eclipse-equinox/equinox.framework#61 and is now moved to this repository due to the merge of the equinox.framework and equinox.bundles repository.
Test case to reproduce: #15
The case is currently designed to be very close to scenario that happens to me where m2e is in involved.
Before this is merged it will likely has to be generalized and simplified.
Instead of a
CountDownLatchinMavenModelManager.HeavyComponentthat is count down inMavenProjectManager.HeavyComponentonly aThread.sleep()could be used or, when being debugged one could place a break-point there.Using a CountDownLatch just reliably ensures that the test passes falsely due to race-conditions and the test does not take unnecessarily long. But it might influence a solution of this problem badly.