fix(e2e): add retry logic for transient workspace lookup in port-forward test#123
Conversation
…ard test The port-forward e2e test intermittently fails with "workspace not found" when Docker is under load from concurrent SSH commands. Add "workspace not found" to retryableSSHPatterns and wrap DevsyPortTest in execWithSSHRetry to give it the same 3-attempt backoff other SSH commands use.
✅ Deploy Preview for devsydev canceled.
|
|
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 29 minutes and 31 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 (3)
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 |
1 participant
Summary
"workspace not found"toretryableSSHPatternsine2e/framework/retry.goso transient workspace lookup failures during Docker load are retriedDevsyPortTestinexecWithSSHRetryto give the port-forward command the same 3-attempt backoff (5s, 10s) that other SSH commands already use