Skip to content

Make nightly versions consistent #9453

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

Merged
merged 2 commits into from
Mar 21, 2025
Merged

Make nightly versions consistent #9453

merged 2 commits into from
Mar 21, 2025

Conversation

mergennachin
Copy link
Contributor

Summary:

Summary:

- Make the git hash from 3/11 nightly consistent with https://hud.pytorch.org/pytorch/pytorch/commit/d962699548c6740bf5d0f3ccda933de3b6fca643
- Make torchtune nightly consistent
Copy link

pytorch-bot bot commented Mar 20, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/9453

Note: Links to docs will display an error until the docs builds have been completed.

❌ 1 New Failure, 1 Cancelled Job

As of commit 3c352fd with merge base 87dd81a (image):

NEW FAILURE - The following job has failed:

CANCELLED JOB - The following job was cancelled. Please retry:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@@ -1 +1 @@
08434df1f2f88c9770e59246caa2ff9c6f613270
295f2ed4d103017f7e19a7b8263ece606cd629db
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Mar 20, 2025
Comment on lines +70 to +72
#
# NOTE: If you're changing, make the corresponding change in .ci/docker/ci_commit_pins/pytorch.txt
# by picking the hash from the same date in https://hud.pytorch.org/hud/pytorch/pytorch/nightly/
Copy link
Contributor

@jathu jathu Mar 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There might be an opportunity to force compliance.

  1. We should create ./tools/setup/pytorch_nightly_version.txt, which hosts this version
  2. In both files, we should read directly from that file
NIGHTLY_VERSION = open("${ROOT}/tools/setup/pytorch_nightly_version.txt", "r").read().strip()
NIGHTLY_VERSION=$(cat "${ROOT}/tools/setup/pytorch_nightly_version.txt")

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

^+1

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, how do we find the mapping between git commit hash and nightly version?

@mergennachin mergennachin merged commit f23616c into main Mar 21, 2025
256 of 260 checks passed
@mergennachin mergennachin deleted the update_nightly_2 branch March 21, 2025 01:13
oscarandersson8218 pushed a commit to oscarandersson8218/executorch that referenced this pull request Mar 21, 2025
Summary:

- Make the git hash from 3/11 nightly consistent with
https://hud.pytorch.org/pytorch/pytorch/commit/d962699548c6740bf5d0f3ccda933de3b6fca643
- Make torchtune nightly consistent
DannyYuyang-quic pushed a commit to CodeLinaro/executorch that referenced this pull request Apr 2, 2025
Summary:

- Make the git hash from 3/11 nightly consistent with
https://hud.pytorch.org/pytorch/pytorch/commit/d962699548c6740bf5d0f3ccda933de3b6fca643
- Make torchtune nightly consistent
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. topic: not user facing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants