Skip to content
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

Running couch-start script fails with rate limiting error #9169

Open
garethbowen opened this issue Jun 10, 2024 · 1 comment
Open

Running couch-start script fails with rate limiting error #9169

garethbowen opened this issue Jun 10, 2024 · 1 comment
Assignees
Labels
Flaky Indicates a flaky or unreliable test Testing Affects how the code is tested Type: Technical issue Improve something that users won't notice

Comments

@garethbowen
Copy link
Member

Describe the issue

CI fails sometimes with a rate limit exception trying to download couch.

eg: https://github.com/medic/cht-core/actions/runs/9416969236/job/25941195785

Run ./scripts/ci/couch-start
Unable to find image 'public.ecr.aws/medic/cht-couchdb:4.2.2' locally
docker: Error response from daemon: toomanyrequests: Rate exceeded.
See 'docker run --help'.
Error: Process completed with exit code 125.

Restarting the build works.

Describe the improvement you'd like

Add a retry with a cooldown either to the GH build step, or to the script itself.

Describe alternatives you've considered

  • Investigate why we need to install Couch in this step - I think it's for integration testing, but maybe we should do that as a separate job to make the unit test job super fast.
  • Consider using a tool like docker helper to install the CHT stack instead of this custom couch install script. This gets the retry for free, increases reuse, and tests our own dog food.
@garethbowen garethbowen added Type: Technical issue Improve something that users won't notice Testing Affects how the code is tested Flaky Indicates a flaky or unreliable test labels Jun 10, 2024
@dianabarsan dianabarsan self-assigned this Jun 10, 2024
@dianabarsan
Copy link
Member

I've been wanting to fix this for a LONG time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Flaky Indicates a flaky or unreliable test Testing Affects how the code is tested Type: Technical issue Improve something that users won't notice
Projects
None yet
Development

No branches or pull requests

2 participants