Final changes necessary to auto-update PyTorch version #1438
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This avoids the need to create, approve, and merge a separate PR, in addition to avoiding unnecessary CI runs for the PyTorch version update.
This patch schedules the RollPyTorch action to be run at noon UTC, which roughly corresponds to 4am Pacific Time. We pick this time since the commit for PyTorch nightly releases are picked just after midnight Pacific Time and the nightly release artifacts are produced in about 2 to 3 hours after the commit is picked.
qedawkins
pushed a commit
to nod-ai/torch-mlir
that referenced
this pull request
Oct 3, 2022
Move `onnx-mlir` version to `0.3.0` from `0.2.0`. `1.0.0` was a mistake. Signed-off-by: Whitney Tsang <whitneyt@ca.ibm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains two commits. The first commit pushes the PyTorch version update directly to the main branch, so that we avoid the PR + CI + Approval + Merging steps. The second commit schedules this workflow to be scheduled daily.
I checked that the workflow runs as expected and pushes the change to the main branch if the tests pass (see commit 15e1c45).