[CI] Move benchmarks to the nightly run, label opt-in on PRs#3982
Open
vmoens wants to merge 2 commits into
Open
[CI] Move benchmarks to the nightly run, label opt-in on PRs#3982vmoens wants to merge 2 commits into
vmoens wants to merge 2 commits into
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/rl/3982
Note: Links to docs will display an error until the docs builds have been completed. ⏳ No Failures, 24 PendingAs of commit f1514b9 with merge base a74b478 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This was referenced Jul 9, 2026
This was referenced Jul 9, 2026
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
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.
Stack from ghstack (oldest at bottom):
Benchmarks cost 2 x ~40-60 min GPU jobs on every push to main and on
every PR push, while their only consumers are trend dashboards.
orchestrator's daily workflow_call becomes the sole feed of the
gh-pages trend: its skip-upload flag now derives from the run mode
(upload in "full" mode only, so dry-run and smoke-test runs cannot
touch gh-pages). workflow_dispatch remains for on-demand runs.
"labeled" trigger type so applying the label starts the comparison
immediately.
skipped and no artifacts exist, instead of failing on an empty
download.
Accepted tradeoffs: the trend granularity drops from per-push to
daily, and the 200% regression alert now implicates a day of commits
rather than a single push.
Co-Authored-By: Claude Fable 5 noreply@anthropic.com