Skip to content

[upstream_ut] RuntimeError: _histc_xpu does not have a deterministic implementation, but you set 'torch.use_deter #15

Draft
Stonepia wants to merge 1 commit into
mainfrom
agent/issue-2512
Draft

[upstream_ut] RuntimeError: _histc_xpu does not have a deterministic implementation, but you set 'torch.use_deter #15
Stonepia wants to merge 1 commit into
mainfrom
agent/issue-2512

Conversation

@Stonepia

Copy link
Copy Markdown
Collaborator

[upstream_ut] RuntimeError: _histc_xpu does not have a deterministic implementation, but you set 'torch.use_deter

Fixes intel/torch-xpu-ops#2512

Root Cause: The bundled third_party/torch-xpu-ops copy of SummaryOps.cpp (line 45) calls alertNotDeterministic("_histc_xpu") without the "with floating point input" qualifier, and also calls it unconditionally (no floating-point type check). The local torch-xpu-ops repo has been updated to guard the alert with if (at::isFloatingType(self.scalar_type())) and use the message "_histc_xpu with floating point input", but this fix was not synced into pytorch/third_party/torch-xpu-ops. The test expects the message prefix "_histc_xpu with floating point input" which only matches the updated local version.

Failed Tests:

  • test_torch_xpu.py::TestTorchDeviceTypeXPU::test_nondeterministic_alert_histc_xpu_float32

Diff stat:

.../_internal/common_methods_invocations.py        | 22 +++++++++++++---------
 1 file changed, 13 insertions(+), 9 deletions(-)

[upstream_ut]  RuntimeError: _histc_xpu does not have a deterministic implementation, but you set 'torch.use_deter
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.

[upstream_ut] RuntimeError: _histc_xpu does not have a deterministic implementation, but you set 'torch.use_deter

1 participant