-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flaky e2e test #611
Labels
Comments
This issue is stale because it has been open 60 days with no activity. |
E2E nightly runs are disabled, but that does not mean it's fixed. |
This issue was closed because it has been stalled for 365 days with no activity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What happened:
E2E test is not consistent, as I see because it hits rate limit when it tries to pull the image.
What did you expect to happen:
E2E test is consistent. Potential fix: if it hits rate limit, wait 2 minutes (or I don't know long, check service rate limiting docs). This extra would occur only if it hits rate limit, so it shouldn't cause significant slow down on average.
How to reproduce it:
![image](https://user-images.githubusercontent.com/183191/209303902-87db2ee7-fff2-4dfb-8c45-4349f395923b.png)
Anything else you would like to add:
https://github.com/weaveworks-liquidmetal/flintlock/actions/runs/3745123487/jobs/6359213483
The text was updated successfully, but these errors were encountered: