-
Notifications
You must be signed in to change notification settings - Fork 564
[Proposal] CI HuggingFace Call Reduction #1291
Copy link
Copy link
Open
Labels
complexity-moderateModerately complicated issues for people who have intermediate experience with the codeModerately complicated issues for people who have intermediate experience with the codeenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomerslow-priorityMaintainers are not prioritising this work currently.Maintainers are not prioritising this work currently.
Metadata
Metadata
Assignees
Labels
complexity-moderateModerately complicated issues for people who have intermediate experience with the codeModerately complicated issues for people who have intermediate experience with the codeenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomerslow-priorityMaintainers are not prioritising this work currently.Maintainers are not prioritising this work currently.
Proposal
Reduce HuggingFace calls done during the test suite in CI (Compatibility checks for 3.10, 3.11, 3.12 and Full Code Coverage Checks)
Motivation
Currently if more than one PR, branch update, or release are running at one time, we hit a HuggingFace rate limit error 429, which causes CI to fail erroneously.
Pitch
There are multiple ways we could go about this:
cancel-in-progressor concurrency checks to reduce the frequency of runs or restrict them from running at the same time. The flaw in limiting concurrency is an elongated feedback loop for contributors, we'd like to avoid this if possible.Additional context
GitHub concurrency docs
Checklist