[
https://issues.apache.org/jira/browse/SOLR-18025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18045475#comment-18045475
]
ASF subversion and git services commented on SOLR-18025:
--------------------------------------------------------
Commit 0d5b7262bfc1c1be829a7ff4a6331f7ede606cc1 in solr's branch
refs/heads/branch_10x from Jan Høydahl
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=0d5b7262bfc ]
SOLR-18025 Test LeaderTragicEventTest flaky (#3939)
Fix by implementing 3 retries
(cherry picked from commit 5d8220c599fa097d8a163c00899f9e5461dd7aae)
> LeaderTragicEventTest is flaky
> ------------------------------
>
> Key: SOLR-18025
> URL: https://issues.apache.org/jira/browse/SOLR-18025
> Project: Solr
> Issue Type: Improvement
> Components: Tests
> Reporter: Jan Høydahl
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> LeaderTragicEventTest shows significant flakiness in CI builds over the last
> 28 days:
> - 42 flaky test occurrences (4% flaky rate)
> - 1,110 passed occurrences (96%)
> - Mean execution time: 8.0 seconds
>
> This test is related to LUCENE-8692 where IndexWriter.getTragicException()
> may not reflect all corrupting exceptions. The test uses
> MockDirectoryWrapper's corruptFiles to introduce corruption and expects the
> leader to give up leadership, but this doesn't always happen reliably.
> Multiple Jenkins build failures observed across Solr-Test-10.x,
> Solr-Test-10.0, and Solr-Test-main.
> Should we consider marking as @BadApple annotation?
> Test Location:
> solr/core/src/test/org/apache/solr/cloud/LeaderTragicEventTest.java
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
