Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-7603

Scary non reproducible failure from UpdateRequestProcessorFactoryTest.testUpdateDistribChainSkipping

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.3, 6.0
    • Component/s: None
    • Labels:
      None

      Description

      jenkins nightly hit a very inexplicable error today...

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

      ...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 got got the "RunAlways" annotation indicating it should always be included in the chain (everything before hte DistribUpdateProcessor is normally)

      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?

        Attachments

          Activity

            People

            • Assignee:
              hossman Hoss Man
              Reporter:
              hossman Hoss Man
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: