fix(tests): stabilize cluster restart on arm64#241
Conversation
yordis
commented
May 9, 2026
- ARM64 runners have less timing headroom while the full suite is under load.
- This fixture repeatedly restarts a three-node cluster, so noisy scheduling can produce false red builds unrelated to the PR being validated.
- Keeping this fixture isolated reduces wasted CI cycles on unrelated changes.
Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
PR SummaryLow Risk Overview The test now uses longer stabilization/restart/Given timeouts on ARM64 to reduce CI flakiness during repeated 3-node cluster restarts. Reviewed by Cursor Bugbot for commit 41aa74d. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |