Skip to content
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.

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

[v1.5.0] float2::x and float2::y may not be the same as float on ROCm… #35783

Merged
merged 1 commit into from
Mar 31, 2020

Conversation

gchanan
Copy link
Contributor

@gchanan gchanan commented Mar 31, 2020

… (#35593)

Summary:
This causes ambiguity and can be triggered sometimes (e.g., by #35217). Explicitly convert them to float.

error: conditional expression is ambiguous; 'const
hip_impl::Scalar_accessor<float, Native_vec_, 0>' can be converted to
'float' and vice versa

Pull Request resolved: #35593

Differential Revision: D20735663

Pulled By: ezyang

fbshipit-source-id: ae6a38a08e59821bae13eb0b9f9bdf21a008d5c0

…pytorch#35593)

Summary:
This causes ambiguity and can be triggered sometimes (e.g., by pytorch#35217). Explicitly convert them to float.

    error: conditional expression is ambiguous; 'const
    hip_impl::Scalar_accessor<float, Native_vec_, 0>' can be converted to
    'float' and vice versa
Pull Request resolved: pytorch#35593

Differential Revision: D20735663

Pulled By: ezyang

fbshipit-source-id: ae6a38a08e59821bae13eb0b9f9bdf21a008d5c0
@dr-ci
Copy link

dr-ci bot commented Mar 31, 2020

💊 CircleCI build failures summary and remediations

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


  • 1/1 failures introduced in this PR

🕵️ 1 new failure recognized by patterns

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

See CircleCI build pytorch_linux_backward_compatibility_check_test (1/1)

Step: "Test" (full log | pattern match details) <confirmed not flaky by 2 failures>

Mar 31 23:32:09 The PR is introducing backward incompatible changes to the operator library. Please contact PyTorch team to confirm whether this change is wanted or not.
Mar 31 23:32:09 processing existing schema:  aten::sparse_coo_tensor.size(int[] size, *, int dtype, int layout, Device device, bool pin_memory=False) -> (Tensor) 
Mar 31 23:32:09 processing existing schema:  aten::sparse_coo_tensor.indices(Tensor indices, Tensor values, *, int? dtype=None, int? layout=None, Device? device=None, bool? pin_memory=None) -> (Tensor) 
Mar 31 23:32:09 processing existing schema:  aten::sparse_coo_tensor.indices_size(Tensor indices, Tensor values, int[] size, *, int? dtype=None, int? layout=None, Device? device=None, bool? pin_memory=None) -> (Tensor) 
Mar 31 23:32:09 processing existing schema:  aten::split_with_sizes(Tensor self, int[] split_sizes, int dim=0) -> (Tensor[]) 
Mar 31 23:32:09 processing existing schema:  aten::squeeze(Tensor(a) self) -> (Tensor(a)) 
Mar 31 23:32:09 processing existing schema:  aten::squeeze.dim(Tensor(a) self, int dim) -> (Tensor(a)) 
Mar 31 23:32:09 processing existing schema:  aten::stft(Tensor self, int n_fft, int? hop_length=None, int? win_length=None, Tensor? window=None, bool normalized=False, bool onesided=True) -> (Tensor) 
Mar 31 23:32:09 skipping schema:  aten::sub_.Tensor(Tensor(a!) self, Tensor other, *, Scalar alpha=1) -> (Tensor(a!)) 
Mar 31 23:32:09 skipping schema:  aten::sub_.Scalar(Tensor(a!) self, Scalar other, Scalar alpha=1) -> (Tensor(a!)) 
Mar 31 23:32:09 processing existing schema:  aten::t(Tensor(a) self) -> (Tensor(a)) 
Mar 31 23:32:09 The PR is introducing backward incompatible changes to the operator library. Please contact PyTorch team to confirm whether this change is wanted or not.  
Mar 31 23:32:09  
Mar 31 23:32:09 Broken ops: [ 
Mar 31 23:32:09 	aten::local_value(RRef(t) self) -> (t) 
Mar 31 23:32:09 	_aten::full(int[] size, Scalar fill_value, *, int? dtype=None, int? layout=None, Device? device=None, bool? pin_memory=None) -> (Tensor) 
Mar 31 23:32:09 	_aten::dequantize(Tensor self) -> (Tensor) 
Mar 31 23:32:09 	_aten::quantize_per_tensor(Tensor self, float scale, int zero_point, int dtype) -> (Tensor) 
Mar 31 23:32:09 	_aten::div.Tensor(Tensor self, Tensor other) -> (Tensor) 
Mar 31 23:32:09 	_aten::detach(Tensor self) -> (Tensor) 
Mar 31 23:32:09 	prim::id(AnyClassType? x) -> (int) 
Mar 31 23:32:09 	aten::owner(RRef(t) self) -> (__torch__.torch.classes.dist_rpc.WorkerInfo) 

This comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions on the GitHub issue tracker.

See how this bot performed.

This comment has been revised 2 times.

gchanan added a commit to gchanan/pytorch that referenced this pull request Mar 31, 2020
This is another case of the issue fixed in pytorch#35783,
but it triggers reliably on the 1.5.0 branch.
@gchanan
Copy link
Contributor Author

gchanan commented Mar 31, 2020

Going to merge this because it looks like it half fixes the problem, see master PR #35784 for more.

@gchanan gchanan merged commit 165403f into pytorch:release/1.5 Mar 31, 2020
xuhdev pushed a commit to xuhdev/pytorch that referenced this pull request Apr 1, 2020
This is another case of the issue fixed in pytorch#35783,
but it triggers reliably on the 1.5.0 branch.
gchanan added a commit to gchanan/pytorch that referenced this pull request Apr 1, 2020
This is another case of the issue fixed in pytorch#35783,
but it triggers reliably on the 1.5.0 branch.
gchanan added a commit that referenced this pull request Apr 1, 2020
This is another case of the issue fixed in #35783,
but it triggers reliably on the 1.5.0 branch.
gchanan added a commit that referenced this pull request Apr 1, 2020
This is another case of the issue fixed in #35783,
but it triggers reliably on the 1.5.0 branch.

ghstack-source-id: ef64586009f0af7f60291f8b23162a59b2b9fe75
Pull Request resolved: #35817
gchanan added a commit to gchanan/pytorch that referenced this pull request Apr 1, 2020
This is another case of the issue fixed in pytorch#35783,
but it triggers reliably on the 1.5.0 branch.
gchanan added a commit that referenced this pull request Apr 1, 2020
This is another case of the issue fixed in #35783,
but it triggers reliably on the 1.5.0 branch.

[ghstack-poisoned]
gchanan added a commit that referenced this pull request Apr 1, 2020
This is another case of the issue fixed in #35783,
but it triggers reliably on the 1.5.0 branch.

ghstack-source-id: 676a0d6445d9bfce26e38c394add48863610f089
Pull Request resolved: #35839
facebook-github-bot pushed a commit that referenced this pull request Apr 1, 2020
…Cm (#35785)

Summary:
This is another case of the issue fixed in #35783. Mirroring 35786.
Pull Request resolved: #35785

Differential Revision: D20800317

Pulled By: ezyang

fbshipit-source-id: de5f32839755d5ff5aefff8408df69adbab4d0a1
gchanan added a commit that referenced this pull request Apr 2, 2020
…Cm (#35785)

Summary:
This is another case of the issue fixed in #35783. Mirroring 35786.
Pull Request resolved: #35785

Differential Revision: D20800317

Pulled By: ezyang

fbshipit-source-id: de5f32839755d5ff5aefff8408df69adbab4d0a1
Rednickle pushed a commit to Rednickle/redttorch that referenced this pull request Apr 20, 2020
…Cm (#35785)

Summary:
This is another case of the issue fixed in pytorch/pytorch#35783. Mirroring 35786.
Pull Request resolved: pytorch/pytorch#35785

Differential Revision: D20800317

Pulled By: ezyang

fbshipit-source-id: de5f32839755d5ff5aefff8408df69adbab4d0a1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants