Commit Graph

5 Commits (2ba71af651edef93a39ce6d1c0f05ff12b0d25e0)

Author SHA1 Message Date
Roll PyTorch Action 7da1af85c2 update PyTorch version to 1.13.0.dev20221003 2022-10-03 16:35:07 +00:00
Roll PyTorch Action f32869b854 update PyTorch version to 1.13.0.dev20221002 2022-10-02 17:09:55 +00:00
Roll PyTorch Action aa31be720a update PyTorch version to 1.13.0.dev20220930 2022-09-30 13:27:54 +00:00
Roll PyTorch Action 15e1c45ed6 update PyTorch version to 1.13.0.dev20220929 2022-09-29 20:34:45 +00:00
Ashay Rane 53e76b8ab6
build: create RollPyTorch to update PyTorch version in Torch-MLIR (#1419)
This patch fetches the most recent nightly (binary) build of PyTorch,
before pinning it in pytorch-requirements.txt, which is referenced in
the top-level requirements.txt file.  This way, end users will continue
to be able to run `pip -r requirements.txt` without worrying whether
doing so will break their Torch-MLIR build.

This patch also fetches the git commit hash that corresponds to the
nightly release, and this hash is passed to the out-of-tree build so
that it can build PyTorch from source.

If we were to sort the torch versions as numbers (in the usual
descending order), then 1.9 appears before 1.13.  To fix this problem,
we use the `--version-sort` flag (along with `--reverse` for specifying
a descending order).  We also filter out lines that don't contain
version numbers by only considering lines that start with a digit.

As a matter of slight clarity, this patch renames the variable
`torch_from_src` to `torch_from_bin`, since that variable is initialized
to `TM_USE_PYTORCH_BINARY`.

Co-authored-by: powderluv <powderluv@users.noreply.github.com>
2022-09-28 15:38:30 -05:00