-
Notifications
You must be signed in to change notification settings - Fork 105
Enable windows arm64 builds for vision #6352
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
@alinpahontu2912 is attempting to deploy a commit to the Meta Open Source Team on Vercel. A member of the Team first needs to authorize it. |
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.
Would it be possible to add a testing workflow here to validate that we don't break things whenever we make changes?
Also not a huge fan of batch and the fact that 3/5 of these scripts are copy / pasted from the For now this is fine, I'm going to set a reminder for myself in 6 months (September 25, 2025) to check on this and if these aren't updated to something other than batch I'm going to recommend we remove them. |
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.
Going to take a bit of a harder stance on this and say that we shouldn't add new batch at all here.
I know this is inconvenient but I want to hold a higher bar for these since we should be intentional about when we decide to take things on for maintenance and we're purposefully choosing now to not maintain batch.
Please update this PR to convert the batch to either bash
or python
needs: generate-matrix | ||
strategy: | ||
fail-fast: false | ||
matrix: |
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.
Do we also want to test audio here as well?
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.
Does it matter which one we use in the testing workflow? I thought this worklflow is supposed to just to check if anything starts breaking, so does it make a difference if we use audio or vision?
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.
Well if you want to test if this works across vision and audio it might make sense to test both of them here
The arm64 build will fail since the new workflow depends on the changes from the torchvision repository: pytorch/vision#8947. |
hey @seemethere can you please re-trigger the tests? we do not have the permissions to do so. |
I retriggered them for you. |
Hey, @zxiiro or @seemethere can you retrigger them again? |
Done |
Thank you very much @zxiiro, can you try again, please? |
Hey @seemethere @zxiiro can you retrigger again please ? |
Hey @malfet @seemethere can you run the workflows again ? |
Hey @zxiiro, thanks lot for the very fast replies, can you rerun the tests again, please? |
No problem! |
Hey, @zxiiro, can you do it again? |
Hey @seemethere @malfet can you take a look again and merge this? |
Add scripts and workflow for enabling windows arm64 builds
Add scripts and workflow for enabling windows arm64 builds