-
Notifications
You must be signed in to change notification settings - Fork 7k
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
Adding tagged builds for M1 #6140
Conversation
shell: arch -arch arm64 bash {0} | ||
env: | ||
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_PYTORCH_UPLOADER_ACCESS_KEY_ID }} | ||
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_PYTORCH_UPLOADER_SECRET_ACCESS_KEY }} | ||
CHANNEL: nightly |
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.
Err, this will fail for nightly builds, isn't it (I.e. Set CHANNEL (only for tagged pushes)
would only set it to test, but what will set it to nightly?
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.
please see comment below we do set CHANNEL nightly by default
@@ -113,9 +143,8 @@ jobs: | |||
shell: arch -arch arm64 bash {0} | |||
env: | |||
CONDA_PYTORCHBOT_TOKEN: ${{ secrets.CONDA_PYTORCHBOT_TOKEN }} | |||
UPLOAD_CHANNEL: nightly |
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.
Same as above, what will set a channel environment variable to nightly
for regular builds?
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.
please see comment below we do set CHANNEL nightly by default
fi | ||
export BUILD_VERSION="$_VERSION_BASE.dev$(date "+%Y%m%d")$VERSION_SUFFIX" | ||
BUILD_VERSION="$BUILD_VERSION.dev$(date "+%Y%m%d")$VERSION_SUFFIX" |
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.
I'm not a bash expert, doesn't one need to re-export it here?
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.
yes totally its re-exported at line 119 below
workflow_dispatch: | ||
env: | ||
CHANNEL: "nightly" |
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.
Here is where we set default CHANNEL to nightly
@atalman @malfet FYI, it seems that the unit-tests are failing on M1. We haven't been able to pinpoint the Core commit that broke it but it looks less likely we will be able to release M1 binaries for TorchVision. We've added all the details that we know so far at pytorch/pytorch#79421. Please let us know what you think. |
Hey @atalman! You merged this PR, but no labels were added. The list of valid labels is available at https://github.com/pytorch/vision/blob/main/.github/process_commit.py |
Summary: Adding tagged builds for torchaudio see: pytorch/vision#6140 Pull Request resolved: #2471 Reviewed By: hwangjeff Differential Revision: D37080828 Pulled By: atalman fbshipit-source-id: 13d754f522510514f0148ba465ce12a320058722
* Adding tagged builds * Testing * Testing * Testing * Testing * Adding conda builds
Summary: Adding tagged builds for torchaudio see: pytorch/vision#6140 Pull Request resolved: pytorch#2471 Reviewed By: hwangjeff Differential Revision: D37080828 Pulled By: atalman fbshipit-source-id: 13d754f522510514f0148ba465ce12a320058722
Summary: Adding tagged builds for torchaudio see: pytorch/vision#6140 Pull Request resolved: #2471 Reviewed By: hwangjeff Differential Revision: D37080828 Pulled By: atalman fbshipit-source-id: 13d754f522510514f0148ba465ce12a320058722
* Adding tagged builds * Testing * Testing * Testing * Testing * Adding conda builds
* Add M1 wheels binary builds (#5948) * [M1] Set build version and delocate wheels (#6110) This would package libpng and libjpeg.dylib into wheel files Add a very simple test step, copied from https://github.com/pytorch/pytorch.github.io/blob/1eaa33a3d3f1b83b64c5031c6dd04dbb238d6105/scripts/test_install.py#L78 Cherry-picked from https://github.com/pytorch/builder/blob/d0bc74cc363a9da5a8b6a40e883d40d25d050036/build_m1_domains.sh#L22 * [BE] Unify version computation (#6117) * [BE] Unify version computation Instead of hardcoding dev version in various script, use one from `version.txt` if `setup_build_version` is called without arguments Also, pass `--pre` option to M1 build/test pip install commands to build TorchVision against nightly pytorch * Pin torchvision dependency to a specific pytorch version * [M1] Install "jpeg<=9b" rather than OpenJpeg (#6122) Explicitly set PATH to point to `conda` binary, otherwise libjpeg detection logic does not work Pin libjpeg to the same version on x86 and m1 Add simple tests that jpeg can be decoded by a generated wheel * Add unit-tests for M1 (#6132) * Add M1 testing job * libjpeg -> jpeg<=9b in test-m1.yml * Added export PATH=~/miniconda3/bin... from 6122 * Tests were OK, let's see if we can remove the pinning * GH: Add M1 conda build workflows (#6135) Clean up Conda build folder before every run Enable artifact upload to GitHub for every workflow run, but upload to Conda/S3 only on nightly pushes Test plan: `conda install -c pytorch-nightly torchvision; python -c "import torchvision;print(torchvision.io.read_image('hummingbird.jpg').shape)"` * Fix `Test M1` workflow By passing `--pre` option to `pip install`, otherwise torchvision were always tested against last PyTorch release * Adding tagged builds for M1 (#6140) * Adding tagged builds * Testing * Testing * Testing * Testing * Adding conda builds * Fix `if` condition for s3/conda uploads (#6146) Replace `steps.extract_branch.outputs.branch` (which were probably taken from https://stackoverflow.com/questions/58033366/how-to-get-the-current-branch-within-github-actions ) with straightforward `github.event.ref` Tested in https://github.com/malfet/deleteme/runs/6822647720?check_suite_focus=true and https://github.com/malfet/deleteme/runs/6822691158?check_suite_focus=true * Fix typo in GHA nightly build condition (#6158) s#ref/heads/#refs/heads/# I should have noticed it while copy-n-pasting the condition. Unfortunately there are no way to test is other than in prod, but nightly builds are still not getting pushed, see https://github.com/pytorch/vision/runs/6860407007?check_suite_focus=true for example * Making sure we are building against release * Testing Testing Testing Testing testing Testing Testing Testing Testing Testing Testing Testing * Testing * Testing * Cleanup * Refactoring logic Co-authored-by: Nikita Shulga <nshulga@fb.com> Co-authored-by: Nicolas Hug <contact@nicolas-hug.com>
Summary: * Adding tagged builds * Testing * Testing * Testing * Testing * Adding conda builds Differential Revision: D37212653 fbshipit-source-id: b5575a1a6ea4264e0254db66c9ae42f5b3507a18
Summary: * Adding tagged builds * Testing * Testing * Testing * Testing * Adding conda builds Reviewed By: datumbox Differential Revision: D37212653 fbshipit-source-id: 1623f4d510d55a50419921174e9c9b43fffaf7c2
Adding tagged builds for M1