[Ra9huvansh]

Fixes #4428

Problem

MultiDbConnectionProviderFailoverAttemptsConfigTest.delayBetweenFailoverAttempts_permanentExceptionAfterAttemptsExhausted was flaky in CI with: expected: <1> but was: <2>

The test used a 20ms freeze window. The 50-iteration rapid loop could take longer than 20ms on a loaded CI machine, causing the freeze window to expire mid-loop. When that happened, markAsFreeze() succeeded again and incremented failoverAttemptCount to 2, failing the assertEquals(1, ...) assertion.

Fix

• Increase delayMs from 20ms to 200ms so the rapid loop always completes within the freeze window
• Increase atMost from 200ms to 2s proportionally, since the await() block must wait for the (now longer) freeze window to expire
• Relax pollInterval from 10ms to 50ms accordingly
• Remove now-unused import org.awaitility.Durations

No production code changes.

---

Note

Low Risk
Low risk: test-only timing adjustments to reduce CI flakiness; no production logic changes.

Overview
Stabilizes MultiDbConnectionProviderFailoverAttemptsConfigTest.delayBetweenFailoverAttempts_permanentExceptionAfterAttemptsExhausted by widening the failover delay window (20ms � 200ms) so the rapid retry loop stays within the freeze period.

Updates the Awaitility wait/poll timings to match the longer window and removes the unused org.awaitility.Durations import.

^{Reviewed by Cursor Bugbot for commit bc24549. Bugbot is set up for automated code reviews on this repo. Configure here.}

[jit-ci]

Hi, I’m Jit, a friendly security platform designed to help developers build secure applications from day zero with an MVS (Minimal viable security) mindset.

In case there are security findings, they will be communicated to you as a comment inside the PR.

Hope you’ll enjoy using Jit.

Questions? Comments? Want to learn more? Get in touch with us.

[atakavci]

hey @Ra9huvansh ,

thanks for picking this up!
Though this doesn't seem to show up recently, its nice to work on for more stable pipeline.
Let me give it a go for pending workflows.
Meanwhile, lets think about if there is a any better way rather than tuning those durations or relying on timing at all.

[Ra9huvansh]

hi @atakavci, yes indeed relying on just timing is fragile. What could be a better approach? Do you have anything in mind? Also sorry about the formatter, will make sure to run it before pushing next time.

[atakavci]

LGTM