[
https://issues.apache.org/jira/browse/ARIES-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Holly Cummins resolved ARIES-905.
---------------------------------
Resolution: Fixed
I've fixed this by adding Thread.sleep() calls in the test. It's not elegant,
but I think some sort of pausing is necessary when testing asynchronous
occurrences.
> Test failures (with current snapshots):
> ---------------------------------------
>
> Key: ARIES-905
> URL: https://issues.apache.org/jira/browse/ARIES-905
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Reporter: Holly Cummins
> Assignee: Holly Cummins
>
> See https://builds.apache.org/job/AriesWithSnapshotDependencies/196. Now that
> the build which tests all the current snapshots against each other is going,
> it's exposed some test failures in blueprint:
> Test Result (2 failures / +2)
> org.apache.aries.blueprint.itests.TestReferences.testUnaryReference
> [equinox\/3.5.0]
> org.apache.aries.blueprint.itests.TestReferences.testListReferences
> [equinox\/3.5.0]
> To reproduce, change the blueprint-core dependency in blueprint-bundle to
> 1.0.1-SNAPSHOT, and change the blueprint-bundle dependency in
> blueprint-itests to 1.0.1-SNAPSHOT (but don't check those changes in, that's
> what the test build is for).
> It looks like the problem started from r1368206, ARIES-896. The problem
> changes were in the AbstractServiceReferenceRecipe class, which now handles
> service events asynchronously. Since TestReferences doesn't pause for this
> asynchronous handling, we get failures.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira