[
https://issues.apache.org/jira/browse/SOLR-10916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16119130#comment-16119130
]
Steve Rowe commented on SOLR-10916:
-----------------------------------
bq. I'm beasting a change that calls
{{client.getZkStateReader().forceUpdateCollection()}} before adding the doc
Okay, so that idea didn't work - I got 12 failures out of 100 beasting
iterations with this change. Back to the drawing board...
> Any Solr test using MiniSolrCloud or Solr Core's should extend
> SolrTestCaseJ4/SolrCloudTestCase
> -----------------------------------------------------------------------------------------------
>
> Key: SOLR-10916
> URL: https://issues.apache.org/jira/browse/SOLR-10916
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
> Assignee: Steve Rowe
> Fix For: master (8.0), 7.1
>
> Attachments: SOLR-10916.patch, SOLR-10916.patch, SOLR-10916.patch
>
>
> We have a non-trivial number of tests that extend LuceneTestCase directly.
> For "utility" method minded tests, this is fine - but for any test that wants
> to instantiate re-use shared config files to instantiate SolrCores, or
> instances of MiniSolrCloudCluster, this makes these tests really cumbersome
> to maintain and deal with because htye don't leverage the existing
> randomization setup logic in SolrTestCaseJ4.
> we should fix these tests where applicable
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
