[
https://issues.apache.org/jira/browse/ARIES-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291281#comment-13291281
]
Holly Cummins commented on ARIES-859:
-------------------------------------
There definitely seems to be a correlation between that commit and the failure,
and it doesn't *seem* to be sporadic, although it's always hard to tell. As
well as the Jenkins failure, I've seen the failure in three consecutive builds
locally. After doing the following:
cd subsystem
svn merge -r1347690:1344727 .
(that is, backing out ARIES-825), I had a clean build.
A mystery, since I agree with you that blueprint doesn't have any obvious
subsystem dependencies.
> Build break:
> org.apache.aries.blueprint.itests.ASMMultiBundleTest.multiBundleTest
> [equinox/3.5.0] failing
> ---------------------------------------------------------------------------------------------------------
>
> Key: ARIES-859
> URL: https://issues.apache.org/jira/browse/ARIES-859
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Reporter: Holly Cummins
> Priority: Critical
>
> The following build has a new test failure, which I can reproduce
> locally:https://builds.apache.org/job/Aries/1473/.
> It seems to be related to the following commit, under ARIES-825:
> http://svn.apache.org/viewvc?view=revision&revision=1347690
--
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
