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

Mark Miller commented on SOLR-10068:
------------------------------------

I see a bunch of this in the last failed log I looked at:

{noformat}
   [junit4]   2> java.lang.NullPointerException
   [junit4]   2>        at 
org.apache.solr.update.UpdateLog$LogReplayer.doReplay(UpdateLog.java:1671)
   [junit4]   2>        at 
org.apache.solr.update.UpdateLog$LogReplayer.run(UpdateLog.java:1510)
   [junit4]   2>        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
   [junit4]   2>        at 
java.util.concurrent.FutureTask.run(FutureTask.java:266)
   [junit4]   2>        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
   [junit4]   2>        at 
java.util.concurrent.FutureTask.run(FutureTask.java:266)
   [junit4]   2>        at 
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:229)
   [junit4]   2>        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
   [junit4]   2>        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
   [junit4]   2>        at java.lang.Thread.run(Thread.java:745)
{noformat}

> The Nightly test SharedFSAutoReplicaFailoverTest appears to be too fragile.
> ---------------------------------------------------------------------------
>
>                 Key: SOLR-10068
>                 URL: https://issues.apache.org/jira/browse/SOLR-10068
>             Project: Solr
>          Issue Type: Test
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>
> SharedFSAutoReplicaFailoverTest 37.00% screwy 30.00 273.97 @Nightly



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to