You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2013/11/26 19:48:53 UTC

[jira] [Updated] (SOLR-5508) AbstractFullDistribZkTestBase gives false positive if collection fails to init

     [ https://issues.apache.org/jira/browse/SOLR-5508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hoss Man updated SOLR-5508:
---------------------------

    Attachment: SOLR-5508.patch

patch with a "test the test" test demonstrating the lack of failure

> AbstractFullDistribZkTestBase gives false positive if collection fails to init
> ------------------------------------------------------------------------------
>
>                 Key: SOLR-5508
>                 URL: https://issues.apache.org/jira/browse/SOLR-5508
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>         Attachments: SOLR-5508.patch
>
>
> Working on a distrib test for another issue, i discovered that if you subclass AbstractFullDistribZkTestBase (and probably some of it's super classes) and specify config files that have mistakes/inconsistencies in them (or just flat out don't exist) you'll see the expected errors in the logs about being unable to initialize "collection1", but no actual test failure (until/unless you try to talk to the controlClient or cloudClient.
> If the test base classes are going to require a schema & solrconfig and init collection1 as part of the setup (i'm not saying they should -- but the existing ones currently do) then they should do some basic sanity checking that collection1 actually loads properly.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org