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

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

Commit 1574941 from [email protected] in branch 'dev/trunk'
[ https://svn.apache.org/r1574941 ]

SOLR-5628: work arround for this test to avoid whatever bug is in the cloud 
test framework

> Cloud test harness manifesting reproducible failures in 
> TestDistribDocBasedVersion
> ----------------------------------------------------------------------------------
>
>                 Key: SOLR-5628
>                 URL: https://issues.apache.org/jira/browse/SOLR-5628
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>
> Jenkins uncovered a test seed that causes a reproducible IndexWriter 
> assertion failure in TestDistribDocBasedVersion on the 4x branch.  
> McCandless helped dig in and believe that something in the way the solr test 
> framework is setup is causing the test to delete the index dirs before the 
> IndexWriter is being closed.  Meanwhile, it appears that recent changes to 4x 
> have caused the nature of the failure to change, so that now -- in addition 
> to the IndexWriter assertion failure -- the test cleanup also stalls out and 
> the test runner has to terminate some stalled threads.
> details to following in comment, but here's the reproduce line...
> {noformat}
> ant test  -Dtestcase=TestDistribDocBasedVersion -Dtests.seed=791402573DC76F3C 
> -Dtests.multiplier=3 -Dtests.slow=true
> -Dtests.locale=ar_IQ -Dtests.timezone=Antarctica/Rothera 
> -Dtests.file.encoding=US-ASCII
> {noformat}
> And the mail thread regarding this...
> https://mail-archives.apache.org/mod_mbox/lucene-dev/201401.mbox/%3Calpine.DEB.2.02.1401100930260.20275@frisbee%3E



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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

Reply via email to