Skip to content

Conversation

@zengk95
Copy link
Contributor

@zengk95 zengk95 commented Jun 21, 2022

Last week, we had to disable it due to infra issues. We are now re enabling since the infra issues are past.

Test Plan:
Reran this job and it looks OK.

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Jun 21, 2022

🔗 Helpful links

✅ No Failures (0 Pending)

As of commit 50d6f22 (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.

@zengk95 zengk95 changed the title reenable xla [ci] reenable xla Jun 21, 2022
@zengk95 zengk95 marked this pull request as ready for review June 21, 2022 20:31
@zengk95 zengk95 requested a review from a team as a code owner June 21, 2022 20:31
@zengk95
Copy link
Contributor Author

zengk95 commented Jun 21, 2022

@pytorchbot merge -f

@kit1980
Copy link
Contributor

kit1980 commented Jun 21, 2022

@pytorchbot merge -f

There is a merge conflict

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

Merge failed due to Command git -C /home/runner/actions-runner/_work/pytorch/pytorch merge --squash __pull-request-79949__init__ returned non-zero exit code 1

Auto-merging .github/workflows/pull.yml
CONFLICT (content): Merge conflict in .github/workflows/pull.yml
Squash commit -- not updating HEAD
Automatic merge failed; fix conflicts and then commit the result.

Raised by https://github.com/pytorch/pytorch/actions/runs/2538130548

@zengk95
Copy link
Contributor Author

zengk95 commented Jun 21, 2022

@pytorchbot merge -f

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

@zengk95 your PR has been successfully merged.

@github-actions
Copy link
Contributor

Hey @zengk95.
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 22, 2022
Summary:
Last week, we had to disable it due to infra issues. We are now re enabling since the infra issues are past.

Pull Request resolved: #79949
Approved by: https://github.com/seemethere

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

Test plan from GitHub:
Reran this job and it looks OK.

Reviewed By: atalman

Differential Revision: D37327441

Pulled By: zengk95

fbshipit-source-id: dc56d3a736ca7a108fca96e8a42efece0aaf14bb
miladm pushed a commit to miladm/pytorch that referenced this pull request Jun 27, 2022
Last week, we had to disable it due to infra issues. We are now re enabling since the infra issues are past.

Test Plan:
Reran this job and it looks OK.
Pull Request resolved: pytorch#79949
Approved by: https://github.com/seemethere
@zengk95 zengk95 deleted the reenable-xla branch July 6, 2022 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants