-
Notifications
You must be signed in to change notification settings - Fork 684
fix unittest-buck2 -- buck test doesn't imply buck build #11388
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/11388
Note: Links to docs will display an error until the docs builds have been completed. ⏳ No Failures, 103 PendingAs of commit 8751628 with merge base a7a9130 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
noting that tests were green before rebase, but we need to wait for unittest-buck2 to be green before landing |
unittest-buck is green, merging |
When I wrote this, I mistakenly thought that
buck test
would build all non-test targets it was passed, but it doesn't. Fix that, and fix a bunch of builds that we weren't guarding so that CI stays green.