Hoss Man created SOLR-7603:
------------------------------

             Summary: Scary non reproducible failure from 
UpdateRequestProcessorFactoryTest.testUpdateDistribChainSkipping
                 Key: SOLR-7603
                 URL: https://issues.apache.org/jira/browse/SOLR-7603
             Project: Solr
          Issue Type: Bug
            Reporter: Hoss Man


jenkins nightly hit a very inexplicable error today...

{noformat}
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/860/
At revision 1682097
Updating http://svn.apache.org/repos/asf/lucene/dev/branches/branch_5x at 
revision '2015-05-27T14:50:50.016 -0400'
[java-info] java version "1.7.0_72"
[java-info] Java(TM) SE Runtime Environment (1.7.0_72-b14, Oracle Corporation)
[java-info] Java HotSpot(TM) 64-Bit Server VM (24.72-b04, Oracle Corporation)
{noformat}

{noformat}
  [junit4]   2> NOTE: reproduce with: ant test  
-Dtestcase=UpdateRequestProcessorFactoryTest
-Dtests.method=testUpdateDistribChainSkipping -Dtests.seed=4ECABCCFD159BE21 
-Dtests.multiplier=2
-Dtests.nightly=true -Dtests.slow=true 
-Dtests.linedocsfile=/x1/jenkins/lucene-data/enwiki.random.lines.txt
-Dtests.locale=mt_MT -Dtests.timezone=Etc/GMT0 -Dtests.asserts=true 
-Dtests.file.encoding=ISO-8859-1
   [junit4] FAILURE 0.01s J0 | 
UpdateRequestProcessorFactoryTest.testUpdateDistribChainSkipping <<<
   [junit4]    > Throwable #1: java.lang.AssertionError
   [junit4]    >        at 
__randomizedtesting.SeedInfo.seed([4ECABCCFD159BE21:3F2E4219A7B299ED]:0)
   [junit4]    >        at
org.apache.solr.update.processor.UpdateRequestProcessorFactoryTest.testUpdateDistribChainSkipping(UpdateRequestProcessorFactoryTest.java:111)
   [junit4]    >        at java.lang.Thread.run(Thread.java:745)
{noformat}


...the line in question is asserting that when executing a distributed update 
(ie: forwarded from another node), the LogUpdateProcessor is still part of the 
chain because it's conifgured to come after the DistribUpdateProcessor 
(everything before hte DistribUpdateProcessor gets skipped in this case)

There's really no explanation for why the LogUpdateProcessor wouldn't be found 
other then a code bug -- but in that case why doesn't the seed reproduce 
reliably?




--
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