aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Holly Cummins (JIRA)" <>
Subject [jira] [Resolved] (ARIES-905) Test failures (with current snapshots):
Date Fri, 17 Aug 2012 21:27:38 GMT


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:
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>            Reporter: Holly Cummins
>            Assignee: Holly Cummins
> See 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:!default.jspa
For more information on JIRA, see:


View raw message