[MPS] Add test consistency from OpInfo based tests from PR 78504

[kulinseth]

No description provided.

[facebook-github-bot]

🔗 Helpful links

• 🧪  See artifacts and rendered test results at hud.pytorch.org/pr/79532
• 📄  Preview Python docs built from this PR
• 📄  Preview C++ docs built from this PR
• ❓Need help or want to give feedback on the CI? Visit our office hours

❌ 1 New Failures

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

Expand to see more

---

• 1/1 failures introduced in this PR

---

🕵️ 1 new failure recognized by patterns

The following CI failures do not appear to be due to upstream breakages

pull / linux-xenial-py3-clang5-android-ndk-r19c-gradle-custom-build-single-full-jit / build-and-test (1/1)

Step: "Setup Linux" (full log | diagnosis details | 🔁 rerun)

2022-07-01T22:47:35.7955064Z ##[error]Process completed with exit code 125.

2022-07-01T22:47:35.7399693Z ##[group]Run docker run --rm -v "$(pwd)":/v -w /v "${ALPINE_IMAGE}" chown -R "$(id -u):$(id -g)" .
2022-07-01T22:47:35.7400161Z �[36;1mdocker run --rm -v "$(pwd)":/v -w /v "${ALPINE_IMAGE}" chown -R "$(id -u):$(id -g)" .�[0m
2022-07-01T22:47:35.7411921Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-07-01T22:47:35.7412206Z env:
2022-07-01T22:47:35.7412441Z   GIT_DEFAULT_BRANCH: master
2022-07-01T22:47:35.7412795Z   ALPINE_IMAGE: 308535385114.dkr.ecr.us-east-1.amazonaws.com/tool/alpine
2022-07-01T22:47:35.7413095Z ##[endgroup]
2022-07-01T22:47:35.7703497Z Unable to find image '308535385114.dkr.ecr.us-east-1.amazonaws.com/tool/alpine:latest' locally
2022-07-01T22:47:35.7939318Z docker: Error response from daemon: Head "https://308535385114.dkr.ecr.us-east-1.amazonaws.com/v2/tool/alpine/manifests/latest": no basic auth credentials.
2022-07-01T22:47:35.7939764Z See 'docker run --help'.
2022-07-01T22:47:35.7955064Z ##[error]Process completed with exit code 125.
2022-07-01T22:47:35.7986582Z Prepare all required actions
2022-07-01T22:47:35.8030991Z ##[group]Run ./.github/actions/teardown-linux
2022-07-01T22:47:35.8031195Z with:
2022-07-01T22:47:35.8031333Z env:
2022-07-01T22:47:35.8031503Z   GIT_DEFAULT_BRANCH: master
2022-07-01T22:47:35.8031686Z ##[endgroup]
2022-07-01T22:47:35.8046171Z ##[group]Run .github/scripts/wait_for_ssh_to_drain.sh
2022-07-01T22:47:35.8046441Z �[36;1m.github/scripts/wait_for_ssh_to_drain.sh�[0m
2022-07-01T22:47:35.8058173Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-07-01T22:47:35.8058393Z env:

---

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.

[malfet]

This looks pretty identical to This looks very much identical to #79521
Also, change can not be landed as is, as pprint is not a standard dependnecy

And it would be nice if it mentioned issue it fixes

[kulinseth]

This looks pretty identical to This looks very much identical to #79521 Also, change can not be landed as is, as pprint is not a standard dependnecy

Unfortunately it turned out to be the same underlying issue. The issue was related to correctness which we noticed in constan_pad_nd operation. I have approved #79521, after it merges, I will rebase to check-in the test_consistency tests.

[kulinseth]

Rebased the changes, now the PR has only the test consistency in test_mps. @albanD , please take a look.

[albanD]

Thanks for the update!

[kulinseth]

File "/Users/gharunner/actions-runner/_work/pytorch/pytorch/conda-test-env-2519578557/lib/python3.8/site-packages/torchgen/utils.py", line [34](https://github.com/pytorch/pytorch/runs/6946646878?check_suite_focus=true#step:6:35), in <module>
34
    from yaml import CSafeLoader as Loader
[35](https://github.com/pytorch/pytorch/runs/6946646878?check_suite_focus=true#step:6:36)
ModuleNotFoundError: No module named 'yaml'
[36](https://github.com/pytorch/pytorch/runs/6946646878?check_suite_focus=true#step:6:37)

How do we enable yaml dependency for MPS. @albanD

[kulinseth]

@pytorchbot merge

[pytorchmergebot]

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

[github-actions]

Hey @kulinseth.
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.

[frank-wei]

The third party libs are overridden. It is not intentional I think. Please revert it.
cc @kulinseth @malfet @albanD

[malfet]

@pytorchbot revert -m "Unintended submodules updates" -c weird

[pytorchmergebot]

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

[pytorchmergebot]

@kulinseth your PR has been successfully reverted.

[malfet]

LGTM, but please undo submodule updates (which aren't needed, are they?)

[kulinseth]

@pytorchbot merge

[pytorchmergebot]

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

[pytorchmergebot]

Merge failed due to Command git -C /home/runner/actions-runner/_work/pytorch/pytorch rebase origin/master returned non-zero exit code 1

Rebasing (1/1)
Auto-merging test/test_mps.py
CONFLICT (content): Merge conflict in test/test_mps.py
error: could not apply 86304f0358... [MPS] Add test consistency from OpInfo based tests from PR 78504 (#79532)
hint: Resolve all conflicts manually, mark them as resolved with
hint: "git add/rm <conflicted_files>", then run "git rebase --continue".
hint: You can instead skip this commit: run "git rebase --skip".
hint: To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply 86304f0358... [MPS] Add test consistency from OpInfo based tests from PR 78504 (#79532)

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

[kulinseth]

@pytorchbot merge

[pytorchmergebot]

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

[pytorchmergebot]

Merge failed due to Refusing to merge as mandatory check(s) pull failed for rule superuser
Raised by https://github.com/pytorch/pytorch/actions/runs/2602174903

[albanD]

@pytorchbot merge -f

[pytorchmergebot]

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

[github-actions]

Hey @kulinseth.
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.