FlakyTest: testEmptyLedgerLosesQuorumEventually

[liangyepianzhou]

Motivation

Fix flaky test: https://github.com/apache/bookkeeper/actions/runs/18525197327/job/52795009929?pr=4652

Changes

To maintain consistency and reduce future modifications, all assertion timeouts in testEmptyLedgerLosesQuorumEventually that use the format assertTrue(xxx, latch.await(xx)) have been unified to 20 seconds.

These assertion timeouts in this test have been changed several times, with each change only increasing the timeout of one assertion. To avoid repeated modifications in the future, these timeouts in this test have been aligned to the longest timeout value that was previously set.

bookkeeper/bookkeeper-server/src/test/java/org/apache/bookkeeper/replication/BookieAutoRecoveryTest.java

Line 418 in bde9ff2

assertTrue("Should be marked as replicated", latch.await(20, TimeUnit.SECONDS));

[StevenLuMT]

good jobs

[Copilot]

Pull Request Overview

This PR fixes a flaky test by standardizing timeout values in the testEmptyLedgerLosesQuorumEventually test method. The changes align all assertion timeouts to 20 seconds to prevent test failures due to timing inconsistencies.

• Increased timeout values from 5 and 15 seconds to a consistent 20 seconds
• Standardized timeout duration across multiple assertions within the same test
• Addressed flaky test behavior identified in CI builds

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[liangyepianzhou]

/bkbot rerun

[liangyepianzhou]

reopen due to #4665