[
https://issues.apache.org/jira/browse/SOLR-11839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320762#comment-16320762
]
David Smiley commented on SOLR-11839:
-------------------------------------
bq. //TODO this is necessary when -Dtests.iters but why? Some other tests
aren't affected
bq. test() creates an alias, testParse() just does some parser testing. So if
test() runs first, testParse() will fail in the @Before method because an alias
still points to one of the live collections. Simple fix to delete the alias in
@Before.
I see. That explains why this test fails ever since you made a change that
causes collection deletion to fail if it's pointed at by an alias. Do you have
any idea why this doBefore is needed here at all (i.e. you do you understand
the root cause of my comment)? When I ran the tests either from my IDE or Ant,
it worked fine. But when I use Ant with -Dtests.iters=2 or higher, it would
fail every time it got to the second iteration. I don't recall it mattered
that there was a 2nd test method. It's weird.
> Fix test failures resulting from SOLR-11218
> -------------------------------------------
>
> Key: SOLR-11839
> URL: https://issues.apache.org/jira/browse/SOLR-11839
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Erick Erickson
> Assignee: Erick Erickson
>
> Any test that deletes a collection before deleting any alias that points to
> it will start failing. The fix will probably be to order your deletions to
> delete or redefine aliases first.
> > create collections
> > create aliases
> > remove aliases
> > remove collections
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
