Uh oh!
There was an error while loading. Please reload this page.
fix(e2e): increase timeout for container-pull-heavy E2E tests - #222
Conversation
✅ Deploy Preview for devsydev canceled.
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ 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 (4)
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 |
d132c18 to
073080bCompareUpgrade TimeoutShort (3min) to TimeoutModerate (5min) for the up-docker-compose and up-features test suites which frequently timeout due to ghcr.io container pull latency.
073080b to
f6c3d8cCompareUh oh!
There was an error while loading. Please reload this page.
Summary
Upgrades the spec timeout from
TimeoutShort(3min) toTimeoutModerate(5min) for the 4 E2E test suites that frequently timeout due to ghcr.io container image pull latency:up_docker_compose.go(16 specs)config.go(17 specs)up_features.go(22 specs)wsl.go(2 specs)These tests pull container images from ghcr.io during execution, making them sensitive to registry latency. The previous 3-minute timeout was insufficient under typical CI load. The global
TimeoutShortconstant remains unchanged — only these 4 test files are affected.