Skip to content

[xla hash update] update the pinned xla hash#79172

Closed
pytorchmergebot wants to merge 1 commit intomasterfrom
update-xla-commit-hash/2465300074-2-1
Closed

[xla hash update] update the pinned xla hash#79172
pytorchmergebot wants to merge 1 commit intomasterfrom
update-xla-commit-hash/2465300074-2-1

Conversation

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

This PR is auto-generated nightly by this action.
Update the pinned xla hash.

@pytorchmergebot pytorchmergebot requested a review from a team as a code owner June 9, 2022 00:59
@facebook-github-bot
Copy link
Copy Markdown
Contributor

facebook-github-bot commented Jun 9, 2022

🔗 Helpful links

✅ No Failures (0 Pending)

As of commit 1061105 (more details on the Dr. CI page):

Expand to see more

💚 💚 Looks good so far! There are no failures yet. 💚 💚


This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

@pytorchmergebot pytorchmergebot force-pushed the update-xla-commit-hash/2465300074-2-1 branch from 7cdfc9f to 8f82671 Compare June 10, 2022 00:59
@gchanan gchanan added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Jun 10, 2022
@pytorchmergebot pytorchmergebot force-pushed the update-xla-commit-hash/2465300074-2-1 branch 3 times, most recently from 88e0f34 to 10eea12 Compare June 13, 2022 01:00
@pytorchmergebot pytorchmergebot force-pushed the update-xla-commit-hash/2465300074-2-1 branch from 10eea12 to 1061105 Compare June 14, 2022 00:59
@zengk95
Copy link
Copy Markdown
Contributor

zengk95 commented Jun 14, 2022

@pytorchbot merge

@pytorchmergebot
Copy link
Copy Markdown
Collaborator Author

@pytorchbot successfully started a merge job. Check the current status here

@github-actions
Copy link
Copy Markdown
Contributor

Hey @pytorchmergebot.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

facebook-github-bot pushed a commit that referenced this pull request Jun 16, 2022
Summary:
This PR is auto-generated nightly by [this action](https://github.com/pytorch/pytorch/blob/master/.github/workflows/_update-commit-hash.yml).
Update the pinned xla hash.

Pull Request resolved: #79172
Approved by: https://github.com/zengk95

Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/bad7720dde598d4300b6523e2c06e61923a2820a

Reviewed By: malfet

Differential Revision: D37157023

fbshipit-source-id: 37513c692b89bbe1ba688fda5eb49e272c508fc0
@github-actions github-actions Bot deleted the update-xla-commit-hash/2465300074-2-1 branch February 17, 2024 01:51
laurentdupin pushed a commit to laurentdupin/pytorch that referenced this pull request Apr 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla signed Merged open source triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants