Skip to content

[CI] Run tests on internal workers#4321

Merged
Wauplin merged 1 commit into
mainfrom
run-tests-on-internal-workers
Jun 9, 2026
Merged

[CI] Run tests on internal workers#4321
Wauplin merged 1 commit into
mainfrom
run-tests-on-internal-workers

Conversation

@Wauplin

@Wauplin Wauplin commented Jun 8, 2026

Copy link
Copy Markdown
Collaborator

Related slack thread.

Using internal workers should prevent 429 rate limits we are experiencing in the CI. These rate limits are not due to the user account but to the WAF flagging some GH IPs as spam.

TL;DR: should be more reliable

Note: not updating the windows test since internal workers are unix


Note

Low Risk
CI-only runner label change for the Ubuntu job; no application or test logic changes.

Overview
The build-ubuntu Python test matrix no longer uses GitHub-hosted ubuntu-latest runners. It now targets the internal runner group aws-general-8-plus, so Ubuntu CI runs on Hugging Face’s own workers instead of default GitHub IPs.

This is meant to cut down 429 / WAF-related rate limiting that was hitting CI when traffic came from flagged GitHub IP ranges. check-imports and build-windows are unchanged (Windows stays on windows-latest because internal workers are Unix-only).

Reviewed by Cursor Bugbot for commit 458bb5f. Bugbot is set up for automated code reviews on this repo. Configure here.

@bot-ci-comment

bot-ci-comment Bot commented Jun 8, 2026

Copy link
Copy Markdown

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@hanouticelina hanouticelina left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@Wauplin Wauplin merged commit 5e65e8f into main Jun 9, 2026
26 checks passed
@Wauplin Wauplin deleted the run-tests-on-internal-workers branch June 9, 2026 13:02
@huggingface-hub-bot

Copy link
Copy Markdown
Contributor

This PR has been shipped as part of the v1.19.0 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants