[ 
https://issues.apache.org/jira/browse/SOLR-7081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512482#comment-14512482
 ] 

ASF subversion and git services commented on SOLR-7081:
-------------------------------------------------------

Commit 1676024 from [~andyetitmoves] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1676024 ]

SOLR-7081: TestMiniSolrCloudCluster.testBasics tidies up after itself, adds 
collection create/delete/create test case.

TestMiniSolrCloudCluster.testBasics now re-creates the server it removed for 
test purposes,
thus restoring the original NUM_SERVERS count. 
TestMiniSolrCloudCluster.testBasics now also deletes
the collection it created for test purposes (this revision adds 
MiniSolrCloudCluster.deleteCollection
and AbstractDistribZkTestBase.waitForCollectionToDisappear methods).

Sometimes TestMiniSolrCloudCluster.testBasics runs its 
create-collection/search-collection/delete-collection
logic twice, thus creating a create/delete/create-collection test case.

> create/delete/create collection (new test case)
> -----------------------------------------------
>
>                 Key: SOLR-7081
>                 URL: https://issues.apache.org/jira/browse/SOLR-7081
>             Project: Solr
>          Issue Type: Test
>            Reporter: Christine Poerschke
>            Assignee: Ramkumar Aiyengar
>            Priority: Minor
>
> Unexpectedly the second collection create fails (saying that the collection 
> already exists) despite the collection delete having apparently succeeded.
> Collection create/delete/create is probably an uncommon operational sequence 
> but perhaps the test failure indicates that something unexpected is happening 
> elsewhere.
> github pull request and test log extracts to follow.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to