ci: fix slack report job — use AWS runner and authenticated GitHub API calls#46448
Merged
Conversation
Contributor
|
CI Dashboard: View test results in Grafana |
|
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
slack-reportjob fromubuntu-22.04toaws-general-8-plusrunner to avoid GitHub Actions IPs being blocked by the WAF IP reputation list when uploading to HuggingFace Hubactions/setup-pythonstep since AWS runners don't have Python pre-installedGITHUB_TOKENto the script and use it in GitHub API requests (/commits,/pulls) to avoid unauthenticated rate limiting (60 req/hr → 5000 req/hr).get()for API response field access so a rate-limit error response doesn't crash the CI run