test: mitigate clock drift in lima e2e fixture#350
Conversation
Lima has a known issue where the guest OS clock can drift on macOS. This causes issues with certificates, scheduled tasks, and other operations that depend on the system time. This commit mitigates the issue by: - Altering the chronyd configuration to allow for large time jumps - Running `chronyc -a makestep` every time we deploy control plane This fixes the clock drift every time you run one of these make targets: ```sh make deploy-lima-fixture make update-lima-fixture make reset-lima-fixture ```
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 2 minutes and 57 seconds. ⌛ 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 (2)
✨ 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 |
Up to standards ✅🟢 Issues
|
Summary
Lima has a known issue where the guest OS clock can drift on macOS. This causes issues with certificates, scheduled tasks, and other operations that depend on the system time.
This commit mitigates the issue by:
chronyc -a makestepevery time we deploy control planeThis fixes the clock drift every time you run one of these make targets:
Testing