Skip to content

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

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.

Sign up for GitHub

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

Jump to bottom
Closed
Parent: Add extra debug info for the super common "index out of bounds" error.
wants to merge 1 commit into from
Closed

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

wants to merge 1 commit into from

Conversation

@pytorchmergebot
Copy link
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 August 12, 2022 07:40
@pytorchbot
Copy link
Collaborator

@pytorchbot merge -g

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Aug 12, 2022 •
edited
Loading

🔗 Helpful links

✅ No Failures (0 Pending)

As of commit d508173 (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
Copy link
Collaborator Author

@pytorchbot successfully started a merge job. Check the current status here.
The merge job was triggered with the green (-g) flag. This means that your change will be merged once all checks on your PR have passed (ETA: 0-4 Hours). If this is not the intended behavior, feel free to use some of the other merge options in the wiki.
Please reach out to the PyTorch DevX Team with feedback or questions!

@github-actions
Copy link
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 Aug 12, 2022
@pytorchmergebot @facebook-github-bot
[xla hash update] update the pinned xla hash (#83319) (#83319)
9b8a5d7 
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: #83319
Approved by: https://github.com/pytorchbot

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

Reviewed By: atalman

Differential Revision: D38658612

Pulled By: atalman

fbshipit-source-id: 74138a76c04d8e9321531d79b5d775c9da433d55
@github-actions github-actions bot deleted the update-xla-commit-hash/2845233707-67-1 branch February 19, 2024 01:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@pytorchbot pytorchbot pytorchbot approved these changes

Assignees

No one assigned

Labels

cla signed Merged open source

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@pytorchmergebot @pytorchbot @facebook-github-bot