I'm also seeing consistent failures of TestInPlaceUpdatesDistrib, both locally as well as in Jenkins. Seems like it started around the same time as SOLR-12833 was committed.
On Thu, May 2, 2019 at 8:21 PM Ishan Chattopadhyaya <[email protected]> wrote: > > It seems the PeerSyncTest started failing around the time SOLR-12833 > was committed. I am not sure if it is related. > @Andrzej Bialecki, do you have any ideas? > > On Thu, May 2, 2019 at 6:13 PM Erick Erickson <[email protected]> wrote: > > > > http://fucit.org/solr-jenkins-reports/failure-report.html > > > > Anyone with a clue why we are getting so many errors on these tests? > > > > 100% DistributedUpdateProcessorTest > > 100% ShardSplitTest > > 75% PeerSync > > > > > > Something changed recently for this kind of failure rate, we really need to > > address them. I’m on vacation this week, so won’t have any time to do more > > than note them. > > > > Erick > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
