-
Couldn't load subscription status.
- Fork 700
Always run build-presets workflow on PRs/pushes #13243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Stack from ghstack (oldest at bottom): |
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/13243
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New Failures, 1 Unrelated FailureAs of commit 94c4f20 with merge base 4ce7078 ( NEW FAILURES - The following jobs have failed:
BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
Tracking issue: #12962. |
The build-presets workflow currently runs only when the workflow file itself is updated. As we update docs to recommend using presets, we should run this job on all PRs. Note that the Windows preset is currently reporting success despite failing to actually build. I'm intending to resolve that shortly as a follow-up.
The build-presets workflow currently runs only when the workflow file itself is updated. As we update docs to recommend using presets, we should run this job on all PRs.
Note that the Windows preset is currently reporting success despite failing to actually build. I'm intending to resolve that shortly as a follow-up.