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

Hoss Man resolved SOLR-2284.
----------------------------

    Resolution: Fixed

This was dealt with at some point, the following steps...

{code}
echo BOGUS > multicore/core0/data/index/segments_1
echo BOGUS > multicore/core1/data/index/segments_1
ant test -Dtestcase=MergeIndexesEmbeddedTest
ant test -Dtestcase=MultiCoreEmbeddedTest
ant test -Dtestcase=MultiCoreExampleJettyTest
{code}

..now result in tests passing even though the indexes on disk are corrupt

                
> tests should not depend on indexes in example data dirs
> -------------------------------------------------------
>
>                 Key: SOLR-2284
>                 URL: https://issues.apache.org/jira/browse/SOLR-2284
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>             Fix For: 4.0
>
>
> Several tests legitimately use "example" configs as a way of verifying that 
> the configs themselves are valid and load properly.  other tests re-use the 
> example configs to test out of lazyiness.
> In either case, these tests should not be using existing indexes found in the 
> example data directories when running the tests.  example indexes are not 
> cleaned up at the end of test runs, and they are not deleted by "ant clean" a 
> codec or other index incompatibility made on trunk can result in tests that 
> fail because an old example index which the user has not manually cleaned up 
> can not be open by the test.
> tests using example configs (for whatever reason) should always use their own 
> private data directory cleaned up on test completion

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Reply via email to