Hey Clement, yes, thats a home made conflict. Pax Exams working folder is made of 1. temporary folder (system property) and 2. user name ( to avoid permission problems when running tests by different users). So, this setup is made for trouble when running tests in parallel.
To simply fix this, you can set the workingFolder(..) option (maybe dynamically) to a unique folder. But: When using a maven local repository for those builds, be aware this is filebased as well and may corrupt your local repository when downloads of the same artifact for different versions happen at the same time (for example). However, if you feel the Pax Exam unique working folder solution crucial, feel free to add a feature jira request so this could be a simple option in core exam. Toni On Mon, Nov 2, 2009 at 7:50 AM, Clement Escoffier < [email protected]> wrote: > Hi, > > We're using pax:exam, and uses a continuous build system (Bamboo in this > case) to execute automatically the tests. However, yesterday a very strange > issue appeared. Bamboo was executing two builds at the same time, both using > pax:exam. It sounds like the two tests conflict... > > The first test was telling me that a bundle from the other test was not > deployable. > The second test throws bug me about an unresolved constraint (which makes > sense because of the missing bundle...) > > If I run the two build separately (and sequentially) everything works fine. > > Is there something that we can do to avoid such strange conflict ? (it is > really a conflict ?). > > Regards, > > Clement > > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > -- Toni Menzel Independent Software Developer Professional Profile: http://okidokiteam.com [email protected] http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software.
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
