I'll look into the CdcrReplicationDistributedZkTest slowness and failure rate in SOLR-12130 this week
On Tue, Mar 20, 2018 at 8:35 AM, BeastIt BeastIt <beastitoffic...@gmail.com> wrote: > BeastIt Unit Test Beasting Summary Report for Apache Solr Master > > BeastIt gives unit tests a chance to duke it out in a fair but difficult > environment. Each test is beasted and then judged. See a link to the full > reports below. > > Number of Tests: 1099 > Number Passed: 1061 > % Passed: 96.54% > > Ran 30 iterations, 5 at a time > > Markers (Marked tests have one of these markers) > @AwaitsFix: 1 > @BadApple: 9 > @Ignore: 3 > > *** Worst Test - Not Marked (It's your Moby Dick!) > > - TestNonWritablePersistFile 100% mission-failed ' Won't run u/root' > > If you catch that whale, next try > - LIROnShardRestartTest 100% mission-failed '' > > *** New Test(s) Failing?! Sound the alarm, we may have a cowboy here. > > - LeaderVoteWaitTimeoutTest 6% flakey > - ScheduledMaintenanceTriggerTest 13% unreliable > - LIROnShardRestartTest 100% mission-failed > > *** New Failures in Test(s)?! Everything looked so good! > > - TestPrepRecovery 3% flakey was 0,0,0,0 > - TestBulkSchemaConcurrent 3% flakey was 0,0,0,0 > - LeaderVoteWaitTimeoutTest 6% flakey was 0 > - ConcurrentCreateRoutedAliasTest 3% flakey was 0,0,0,0 > - DistribJoinFromCollectionTest 3% flakey was 0,0,0,0 > - TestDeleteCollectionOnDownNodes 3% flakey was 0,0,0,0 > - LegacyCloudClusterPropTest 3% flakey was 0,0,0,0 > > *** Slowest Test > > - CdcrReplicationDistributedZkTest 1748.65 screwy '@BadApple @Nightly ' > Can you speed me up? > > *** Worst Test - Marked (How long must it suffer the mark?) > > - CdcrReplicationDistributedZkTest 40% screwy '@BadApple @Nightly ' > > *** Non Running Tests - Coverage Holes?! > > - ChaosMonkeyShardSplitTest '@Ignore ' > - TestRankQueryPlugin '@Ignore ' > - TestMailEntityProcessor '@Ignore ' > > > Full Reports http://apache-solr.bitballoon.com > > (Report maintained by Mark Miller) >
