KEMBAR78
Disable torch.complex32 dtype by anjali411 · Pull Request #70606 · pytorch/pytorch · GitHub
Skip to content

Conversation

@anjali411
Copy link
Contributor

@anjali411 anjali411 commented Jan 4, 2022

[ghstack-poisoned]
@pytorch-probot
Copy link

pytorch-probot bot commented Jan 4, 2022

CI Flow Status

⚛️ CI Flow

Ruleset - Version: v1
Ruleset - File: https://github.com/pytorch/pytorch/blob/b7b1a6891a12ca666d78920f992f381b55fab725/.github/generated-ciflow-ruleset.json
PR ciflow labels: ciflow/default,ciflow/all

Workflows Labels (bold enabled) Status
Triggered Workflows
caffe2-linux-xenial-py3.7-gcc5.4 ciflow/all, ciflow/cpu, ciflow/linux, ciflow/trunk ✅ triggered
docker-builds ciflow/all, ciflow/trunk ✅ triggered
ios-12-5-1-arm64 ciflow/all, ciflow/ios, ciflow/macos, ciflow/trunk ✅ triggered
ios-12-5-1-arm64-coreml ciflow/all, ciflow/ios, ciflow/macos, ciflow/trunk ✅ triggered
ios-12-5-1-arm64-custom-ops ciflow/all, ciflow/ios, ciflow/macos, ciflow/trunk ✅ triggered
ios-12-5-1-arm64-full-jit ciflow/all, ciflow/ios, ciflow/macos, ciflow/trunk ✅ triggered
ios-12-5-1-arm64-metal ciflow/all, ciflow/ios, ciflow/macos, ciflow/trunk ✅ triggered
ios-12-5-1-x86-64 ciflow/all, ciflow/ios, ciflow/macos, ciflow/trunk ✅ triggered
ios-12-5-1-x86-64-coreml ciflow/all, ciflow/ios, ciflow/macos, ciflow/trunk ✅ triggered
ios-12-5-1-x86-64-full-jit ciflow/all, ciflow/ios, ciflow/macos, ciflow/trunk ✅ triggered
libtorch-linux-xenial-cuda10.2-py3.7-gcc7 ciflow/all, ciflow/cuda, ciflow/libtorch, ciflow/linux, ciflow/trunk ✅ triggered
libtorch-linux-xenial-cuda11.3-py3.7-gcc7 ciflow/all, ciflow/cuda, ciflow/libtorch, ciflow/linux, ciflow/trunk ✅ triggered
linux-bionic-cuda10.2-py3.9-gcc7 ciflow/all, ciflow/cuda, ciflow/linux, ciflow/slow, ciflow/trunk ✅ triggered
linux-bionic-py3.7-clang9 ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/noarch, ciflow/trunk ✅ triggered
linux-docs ciflow/all, ciflow/cpu, ciflow/default, ciflow/docs, ciflow/linux, ciflow/trunk ✅ triggered
linux-docs-push ciflow/all, ciflow/cpu, ciflow/linux, ciflow/scheduled ✅ triggered
linux-vulkan-bionic-py3.7-clang9 ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/trunk, ciflow/vulkan ✅ triggered
linux-xenial-cuda11.3-py3.7-gcc7 ciflow/all, ciflow/cuda, ciflow/default, ciflow/linux, ciflow/trunk ✅ triggered
linux-xenial-cuda11.3-py3.7-gcc7-bazel-test ciflow/all, ciflow/bazel, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/trunk ✅ triggered
linux-xenial-cuda11.3-py3.7-gcc7-no-ops ciflow/all, ciflow/cuda, ciflow/linux, ciflow/trunk ✅ triggered
linux-xenial-py3-clang5-mobile-build ciflow/all, ciflow/default, ciflow/linux, ciflow/mobile, ciflow/trunk ✅ triggered
linux-xenial-py3-clang5-mobile-custom-build-static ciflow/all, ciflow/default, ciflow/linux, ciflow/mobile, ciflow/trunk ✅ triggered
linux-xenial-py3.7-clang7-asan ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/sanitizers, ciflow/trunk ✅ triggered
linux-xenial-py3.7-clang7-onnx ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/onnx, ciflow/trunk ✅ triggered
linux-xenial-py3.7-gcc5.4 ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/trunk ✅ triggered
linux-xenial-py3.7-gcc7 ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/trunk ✅ triggered
linux-xenial-py3.7-gcc7-no-ops ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/trunk ✅ triggered
macos-10-15-py3-arm64 ciflow/all, ciflow/macos, ciflow/trunk ✅ triggered
macos-10-15-py3-lite-interpreter-x86-64 ciflow/all, ciflow/macos, ciflow/trunk ✅ triggered
macos-11-py3-x86-64 ciflow/all, ciflow/macos, ciflow/trunk ✅ triggered
parallelnative-linux-xenial-py3.7-gcc5.4 ciflow/all, ciflow/cpu, ciflow/linux, ciflow/trunk ✅ triggered
periodic-libtorch-linux-bionic-cuda11.5-py3.7-gcc7 ciflow/all, ciflow/cuda, ciflow/libtorch, ciflow/linux, ciflow/scheduled ✅ triggered
periodic-libtorch-linux-xenial-cuda11.1-py3.7-gcc7 ciflow/all, ciflow/cuda, ciflow/libtorch, ciflow/linux, ciflow/scheduled ✅ triggered
periodic-linux-bionic-cuda11.5-py3.7-gcc7 ciflow/all, ciflow/cuda, ciflow/linux, ciflow/scheduled ✅ triggered
periodic-linux-xenial-cuda10.2-py3-gcc7-slow-gradcheck ciflow/all, ciflow/cuda, ciflow/linux, ciflow/scheduled, ciflow/slow, ciflow/slow-gradcheck ✅ triggered
periodic-linux-xenial-cuda11.1-py3.7-gcc7-debug ciflow/all, ciflow/cuda, ciflow/linux, ciflow/scheduled ✅ triggered
periodic-win-vs2019-cuda11.1-py3 ciflow/all, ciflow/cuda, ciflow/scheduled, ciflow/win ✅ triggered
periodic-win-vs2019-cuda11.5-py3 ciflow/all, ciflow/cuda, ciflow/scheduled, ciflow/win ✅ triggered
pytorch-linux-xenial-py3-clang5-android-ndk-r19c-build ciflow/all, ciflow/android, ciflow/cpu, ciflow/linux, ciflow/trunk ✅ triggered
pytorch-linux-xenial-py3-clang5-android-ndk-r19c-gradle-custom-build-single ciflow/all, ciflow/android, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/trunk ✅ triggered
pytorch-linux-xenial-py3-clang5-android-ndk-r19c-gradle-custom-build-single-full-jit ciflow/all, ciflow/android, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/trunk ✅ triggered
win-vs2019-cpu-py3 ciflow/all, ciflow/cpu, ciflow/default, ciflow/trunk, ciflow/win ✅ triggered
win-vs2019-cuda11.3-py3 ciflow/all, ciflow/cuda, ciflow/default, ciflow/trunk, ciflow/win ✅ triggered
Skipped Workflows

You can add a comment to the PR and tag @pytorchbot with the following commands:
# ciflow rerun, "ciflow/default" will always be added automatically
@pytorchbot ciflow rerun

# ciflow rerun with additional labels "-l <ciflow/label_name>", which is equivalent to adding these labels manually and trigger the rerun
@pytorchbot ciflow rerun -l ciflow/scheduled -l ciflow/slow

For more information, please take a look at the CI Flow Wiki.

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Jan 4, 2022

🔗 Helpful links

💊 CI failures summary and remediations

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


  • 2/2 failures introduced in this PR

🕵️ 1 new failure recognized by patterns

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

See GitHub Actions build linux-bionic-py3.7-clang9 / test (xla, 1, 1, linux.2xlarge) (1/1)

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

2022-02-09T18:44:49.9527930Z AttributeError: module 'torch' has no attribute 'complex32'
2022-02-09T18:44:49.9525346Z   File "/opt/conda/lib/python3.7/runpy.py", line 263, in run_path
2022-02-09T18:44:49.9525585Z     pkg_name=pkg_name, script_name=fname)
2022-02-09T18:44:49.9525822Z   File "/opt/conda/lib/python3.7/runpy.py", line 96, in _run_module_code
2022-02-09T18:44:49.9526077Z     mod_name, mod_spec, pkg_name, script_name)
2022-02-09T18:44:49.9526305Z   File "/opt/conda/lib/python3.7/runpy.py", line 85, in _run_code
2022-02-09T18:44:49.9526523Z     exec(code, run_globals)
2022-02-09T18:44:49.9526770Z   File "/var/lib/jenkins/workspace/xla/test/pytorch_test_base.py", line 465, in <module>
2022-02-09T18:44:49.9527031Z     class XLATestBase(DeviceTypeTestBase):
2022-02-09T18:44:49.9527312Z   File "/var/lib/jenkins/workspace/xla/test/pytorch_test_base.py", line 468, in XLATestBase
2022-02-09T18:44:49.9527602Z     torch.half, torch.complex32, torch.complex64, torch.complex128
2022-02-09T18:44:49.9527930Z AttributeError: module 'torch' has no attribute 'complex32'
2022-02-09T18:44:50.1390149Z + cleanup
2022-02-09T18:44:50.1390653Z + retcode=1
2022-02-09T18:44:50.1390854Z + set +x
2022-02-09T18:44:50.1436421Z ##[error]Process completed with exit code 1.
2022-02-09T18:44:50.1513614Z ##[group]Run # Ensure the working directory gets chowned back to the current user
2022-02-09T18:44:50.1513960Z �[36;1m# Ensure the working directory gets chowned back to the current user�[0m
2022-02-09T18:44:50.1514324Z �[36;1mdocker run --rm -v "$(pwd)":/v -w /v "${ALPINE_IMAGE}" chown -R "$(id -u):$(id -g)" .�[0m
2022-02-09T18:44:50.1967645Z shell: /usr/bin/bash -e {0}
2022-02-09T18:44:50.1967847Z env:
2022-02-09T18:44:50.1968062Z   BUILD_ENVIRONMENT: linux-bionic-py3.7-clang9

1 failure not recognized by patterns:

Job Step Action
GitHub Actions ios-12-5-1-arm64-metal / build Unknown 🔁 rerun

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.

@facebook-github-bot facebook-github-bot added the oncall: jit Add this issue/PR to JIT oncall triage queue label Jan 4, 2022
@anjali411 anjali411 requested review from albanD and ngimel January 4, 2022 17:01
@anjali411
Copy link
Contributor Author

@ngimel should we just cherry-pick this for the next release?

anjali411 added a commit that referenced this pull request Jan 4, 2022
ghstack-source-id: 3c9cb13
Pull Request resolved: #70606
@anjali411 anjali411 added module: complex Related to complex number support in PyTorch module: bc-breaking Related to a BC-breaking change and removed oncall: jit Add this issue/PR to JIT oncall triage queue labels Jan 4, 2022
| :attr:`~torch.bfloat16` | ``1.6e-2`` | ``1e-5`` |
+---------------------------+------------+----------+
| :attr:`~torch.float32` | ``1.3e-6`` | ``1e-5`` |
+---------------------------+------------+----------+
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @pmeier

@mruberry mruberry self-requested a review January 4, 2022 17:46
Copy link
Collaborator

@mruberry mruberry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool! (So long as the tests pass.)

Note from offline meeting: @ngimel plans to file a follow-up issue for proper ComplexHalf support

@lezcano lezcano removed their request for review January 5, 2022 08:29
@IvanYashchuk IvanYashchuk removed their request for review January 5, 2022 16:46
Related #69209 (comment)




cc ezyang gchanan anjali411 dylanbespalko mruberry @lezcano nikitaved

[ghstack-poisoned]
Related #69209 (comment)




cc ezyang gchanan anjali411 dylanbespalko mruberry @lezcano nikitaved

[ghstack-poisoned]
@anjali411
Copy link
Contributor Author

@pytorchbot ciflow rerun -l ciflow/all

@ngimel ngimel mentioned this pull request Jan 23, 2022
Related #69209 (comment)




cc ezyang gchanan anjali411 dylanbespalko mruberry @lezcano nikitaved

[ghstack-poisoned]
@anjali411
Copy link
Contributor Author

@anjali411 has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

@anjali411 anjali411 added this to the 1.11.0 milestone Feb 2, 2022
Related #69209 (comment)




cc ezyang gchanan anjali411 dylanbespalko mruberry @lezcano nikitaved

Differential Revision: [D33954861](https://our.internmc.facebook.com/intern/diff/D33954861)

[ghstack-poisoned]
anjali411 added a commit that referenced this pull request Feb 2, 2022
ghstack-source-id: dc959ef
Pull Request resolved: #70606
@anjali411
Copy link
Contributor Author

@anjali411 has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

Related #69209 (comment)




cc ezyang gchanan anjali411 dylanbespalko mruberry @lezcano nikitaved

Differential Revision: [D33954861](https://our.internmc.facebook.com/intern/diff/D33954861)

[ghstack-poisoned]
anjali411 added a commit that referenced this pull request Feb 3, 2022
ghstack-source-id: 483e153
Pull Request resolved: #70606
Related #69209 (comment)




cc ezyang gchanan anjali411 dylanbespalko mruberry @lezcano nikitaved

Differential Revision: [D33954861](https://our.internmc.facebook.com/intern/diff/D33954861)

[ghstack-poisoned]
@anjali411
Copy link
Contributor Author

@JackCaoG I will be cherry-picking this PR in the 1.11 release branch and looks like it'll require an xla side change (remove torch.complex32 from this list https://github.com/pytorch/xla/blob/3bb039c8e8cff30e23394e47bf67443b0c200100/test/pytorch_test_base.py#L467-L469)

@JackCaoG
Copy link
Collaborator

JackCaoG commented Feb 3, 2022

@anjali411 Seems like we only need to remove this dtype from our repo, I can do that and backport to our 1.11 branch.

Related #69209 (comment)




cc ezyang gchanan anjali411 dylanbespalko mruberry @lezcano nikitaved

Differential Revision: [D33954861](https://our.internmc.facebook.com/intern/diff/D33954861)

[ghstack-poisoned]
anjali411 added a commit that referenced this pull request Feb 3, 2022
ghstack-source-id: da6772b
Pull Request resolved: #70606
Related #69209 (comment)




cc ezyang gchanan anjali411 dylanbespalko mruberry @lezcano nikitaved

Differential Revision: [D33954861](https://our.internmc.facebook.com/intern/diff/D33954861)

[ghstack-poisoned]
anjali411 added a commit that referenced this pull request Feb 7, 2022
ghstack-source-id: 8f4ae84
Pull Request resolved: #70606
Related #69209 (comment)




cc ezyang gchanan anjali411 dylanbespalko mruberry @lezcano nikitaved

Differential Revision: [D33954861](https://our.internmc.facebook.com/intern/diff/D33954861)

[ghstack-poisoned]
anjali411 added a commit that referenced this pull request Feb 9, 2022
ghstack-source-id: 856df6d
Pull Request resolved: #70606
@malfet
Copy link
Contributor

malfet commented Feb 15, 2022

@anjali411 correct me if I'm wrong, but 13b403b has been landed in 1.11, so we probably can remove the milestone (and close this PR) after xla change is landed

@JackCaoG
Copy link
Collaborator

@malfet I just merge the pt/xla 1.11 pr. Pytroch/xla 1.11 branch is missing several important prs. I am thinking about recut the 1.11 from master which is a bit easier than me manually porting a bunch of pr at the same time. Will let you know if I do that.

@anjali411
Copy link
Contributor Author

@anjali411 correct me if I'm wrong, but 13b403b has been landed in 1.11, so we probably can remove the milestone (and close this PR) after xla change is landed

yup absolutely!

@anjali411 anjali411 removed this from the 1.11.0 milestone Feb 15, 2022
@facebook-github-bot facebook-github-bot deleted the branch gh/anjali411/138/base March 12, 2022 15:16
@facebook-github-bot facebook-github-bot deleted the gh/anjali411/138/head branch March 12, 2022 15:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla signed module: bc-breaking Related to a BC-breaking change module: complex Related to complex number support in PyTorch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants