[
https://issues.apache.org/jira/browse/CONTINUUM-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493155#comment-14493155
]
Brent N Atkinson commented on CONTINUUM-2751:
---------------------------------------------
Ultimately, the junit 4 conversion does not appear to be the source of the
error here. As described in CONTINUUM-2745, the conversion was done so that the
failure did not cause all subsequent tests to fail due to another test
interaction.
The reason this was not happening locally was that the order test execution was
different than on continuum-ci.a.o. I had to use the ordering and test
exclusion capabilities of surefire to find the right combination of tests to
get them to fail so I could debug it. It was:
In continuum-core's pom.xml:
{noformat}
<runOrder>alphabetical</runOrder>
{noformat}
and on the command line:
{noformat}
mvn -Dtest=DefaultPurgeConfigurationServiceTest,DefaultRepositoryServiceTest
-DfailIfNoTests=false clean test
{noformat}
> Build fails due to test interactions: data not being cleaned consistently
> -------------------------------------------------------------------------
>
> Key: CONTINUUM-2751
> URL: https://issues.apache.org/jira/browse/CONTINUUM-2751
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.5.0
> Reporter: Brent N Atkinson
> Assignee: Brent N Atkinson
> Fix For: 1.5.0
>
>
> Very similar in spirit to CONTINUUM-2736, tests are not well-behaved which is
> leading to build instability. On continuum-ci.a.o, I noticed the builds were
> consistently failing despite the full test suite comprehensively passing
> locally.
> The problem is visible in the build results as the test failure:
> {noformat}
> Results :
> Failed tests:
> testRemoveRepository(org.apache.continuum.repository.DefaultRepositoryServiceTest):
> check # repositories expected:<1> but was:<2>
> Tests run: 150, Failures: 1, Errors: 0, Skipped: 0
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
