[MPS] Fix binary ops between int32 tensor with int64 scalar

[malfet]

For some reason, tensor op scalar does not follow the normal binary promotion rules
So cast output tensor to expected type if needed
It seems that one should have casted input tensors to expected output tensor type, but it does not really work for boolean binary ops, so...
Add output tensor type/shape to cached graph key
Extend TestMPS. test_add_scalars to test for this regression

Fixes #79835

[facebook-github-bot]

🔗 Helpful links

• 🧪  See artifacts and rendered test results at hud.pytorch.org/pr/80220
• 📄  Preview Python docs built from this PR
• ❌ C++ docsfailed to build
• ❓Need help or want to give feedback on the CI? Visit our office hours
• ↩️  [fb-only] Re-run with SSH instructions

❌ 1 New Failures

As of commit 71eb14d (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-docs / build-docs (cpp) (1/1)

Step: "Build cpp docs" (full log | diagnosis details | 🔁 rerun)

2022-06-25T03:57:02.3493039Z ##[error]Process completed with exit code 137.

2022-06-25T03:51:43.8869962Z �[01mwriting output... �[39;49;00m[ 90%] �[32mapi/structat_1_1native_1_1_convolution_descriptor .. api/structtorch_1_1enumtype_1_1k_conv_transpose2_d�[39;49;00m
2022-06-25T03:51:57.9925687Z �[01mwriting output... �[39;49;00m[ 92%] �[32mapi/structtorch_1_1enumtype_1_1k_conv_transpose3_d .. api/structtorch_1_1nn_1_1_huber_loss_impl�[39;49;00m
2022-06-25T03:52:13.5104074Z �[01mwriting output... �[39;49;00m[ 93%] �[32mapi/structtorch_1_1nn_1_1_huber_loss_options .. api/structtorch_1_1nn_1_1functional_1_1_multihead_attention_forward_func_options�[39;49;00m
2022-06-25T03:52:20.4672357Z �[01mwriting output... �[39;49;00m[ 95%] �[32mapi/structtorch_1_1nn_1_1functional_1_1_normalize_func_options .. api/typedef_namespacetorch_1_1nn_1_1functional_1a8318be8a4bab733f842c57a3d54ee3dc�[39;49;00m
2022-06-25T03:52:24.4783854Z �[01mwriting output... �[39;49;00m[ 96%] �[32mapi/typedef_namespacetorch_1_1nn_1_1functional_1a872abe58e376dc403b3bea4259d4d2b5 .. api/typedef_namespacetorch_1_1nn_1afecfb211f39a66e9ed2c0c18d556375f�[39;49;00m
2022-06-25T03:52:35.3250664Z �[01mwriting output... �[39;49;00m[ 98%] �[32mapi/typedef_namespacetorch_1_1python_1_1detail_1a9808c29bfe27f974414c895b4ff37f2f .. api/variable_namespacetorch_1ae4963b260c95c4e846fa7538f1c63638�[39;49;00m
2022-06-25T03:52:37.2403543Z �[01mwriting output... �[39;49;00m[100%] �[32mapi/variable_namespacetorch_1aeaf16f038962bbc7c4a0f57696fa3fb1 .. notes/versioning�[39;49;00m
2022-06-25T03:52:37.2403970Z 
2022-06-25T03:52:37.2482317Z �[01mwaiting for workers...�[39;49;00m
2022-06-25T03:57:02.3038945Z /home/ec2-user/actions-runner/_work/_temp/9858733c-cb33-445a-ad48-9bc369035e45.sh: line 27: 20863 Killed                  docker exec -t "${container_name}" bash -c "sudo chown -R jenkins . && pip install dist/*.whl && ./.circleci/scripts/${DOCS_TYPE}_doc_push_script.sh"
2022-06-25T03:57:02.3493039Z ##[error]Process completed with exit code 137.
2022-06-25T03:57:02.3723783Z Prepare all required actions
2022-06-25T03:57:02.3784601Z ##[group]Run ./.github/actions/chown-workspace
2022-06-25T03:57:02.3784832Z ##[endgroup]
2022-06-25T03:57:02.4354941Z ##[group]Run docker run --rm -v "$(pwd)":/v -w /v "${ALPINE_IMAGE}" chown -R "$(id -u):$(id -g)" .
2022-06-25T03:57:02.4355409Z �[36;1mdocker run --rm -v "$(pwd)":/v -w /v "${ALPINE_IMAGE}" chown -R "$(id -u):$(id -g)" .�[0m
2022-06-25T03:57:02.4967880Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-06-25T03:57:02.4968187Z env:
2022-06-25T03:57:02.4968517Z   ALPINE_IMAGE: 308535385114.dkr.ecr.us-east-1.amazonaws.com/tool/alpine
2022-06-25T03:57:02.4968851Z ##[endgroup]
2022-06-25T03:57:10.7621749Z Post job cleanup.

---

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]

Added test as well, and reworked the logic

[malfet]

@pytorchbot merge

[pytorchmergebot]

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

[github-actions]

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

[malfet]

@pytorchbot revert -m "Did not push the final version of commit" -c weird

[pytorchmergebot]

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

[pytorchmergebot]

@malfet your PR has been successfully reverted.

[malfet]

@pytorchbot merge -f

[pytorchmergebot]

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