Skip to content
This repository has been archived by the owner on Aug 27, 2024. It is now read-only.

GHA jobs fail because of too many requests #72

Closed
jakirkham opened this issue Jul 15, 2024 · 2 comments
Closed

GHA jobs fail because of too many requests #72

jakirkham opened this issue Jul 15, 2024 · 2 comments

Comments

@jakirkham
Copy link
Member

jakirkham commented Jul 15, 2024

Have started seeing GHA jobs fail because of too many request (for example:

#16 ERROR: toomanyrequests: 
------
 > pushing rapidsai/staging:miniforge-cuda-71-cuda12.0.1-base-rockylinux8-py3.9-arm64 with docker:

Should we consider some changes here to mange this?

  1. Reduce number of images built
  2. Add a shared docker pull step to minimize pulls and reuse across builds
  3. Combine all pushes into a single command at the end
  4. Minimize how many jobs are run at once
  5. Other ideas?

Note: This happens with ci-imgs too ( rapidsai/ci-imgs#162 )

@ajschmidt8
Copy link
Member

The quickest solution is probably just to adjust the number of concurrent jobs that are allowed in the matrix workflow:

https://docs.github.com/en/actions/using-jobs/using-a-matrix-for-your-jobs#defining-the-maximum-number-of-concurrent-jobs

@bdice
Copy link
Contributor

bdice commented Aug 27, 2024

Closing in favor of rapidsai/ci-imgs#162, now that miniforge-cuda is being merged into ci-imgs (rapidsai/ci-imgs#167).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants