intel / intel/torch-xpu-ops

[Bug Skip]: AssertionError: Tensor-likes are not close! in test_modules_xpu.py

Open
#4,960 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

random skipped
Dominant language
Python
Stars
113
Forks
129
Avg merge
5d 9h
Merged PRs (30d)
112

Description

🐛 Describe the bug with skip template

This is a random issue. Out of 13 runs, it reproduced twice: first at the 6th run, and the second at the 13th run.

Cases:
op_ut,third_party.torch-xpu-ops.test.xpu.test_modules_xpu.TestModuleXPU,test_non_contiguous_tensors_nn_LazyConv3d_xpu_float32

______ TestModuleXPU.test_cpu_gpu_parity_nn_ConvTranspose1d_xpu_complex32 ______
[gw0] linux -- Python 3.10.20 /__w/torch-xpu-ops/torch-xpu-ops/.venv/bin/python
Unexpected success
----------------------------- Captured stderr call -----------------------------
/__w/torch-xpu-ops/torch-xpu-ops/.venv/lib/python3.10/site-packages/torch/testing/_creation.py:240: UserWarning: ComplexHalf support is experimental and many operators don't support it yet. (Triggered internally at /localdisk/home/jenkins/actions-runner/_work/torch-xpu-ops/torch-xpu-ops/pytorch/aten/src/ATen/EmptyTensor.cpp:54.)
  result = torch.empty(shape, device=device, dtype=dtype)
_____ TestModuleXPU.test_non_contiguous_tensors_nn_LazyConv3d_xpu_float32 ______
[gw4] linux -- Python 3.10.20 /__w/torch-xpu-ops/torch-xpu-ops/.venv/bin/python
Traceback (most recent call last):
  File "/__w/torch-xpu-ops/torch-xpu-ops/pytorch/third_party/torch-xpu-ops/test/xpu/../../../../test/test_modules.py", line 442, in test_non_contiguous_tensors
    self.assertEqual(param_grad, default_param_grad)
  File "/__w/torch-xpu-ops/torch-xpu-ops/.venv/lib/python3.10/site-packages/torch/testing/_internal/common_utils.py", line 4879, in assertEqual
    raise error_metas.pop()[0].to_error(  # type: ignore[index]
AssertionError: Tensor-likes are not close!
Versions

Pytorch:
b5540e0ee69e8c2c170b3a65c913411b7a7cc0a9

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with test_modules.py at line 442 and the TestModuleXPU.test_non_contiguous_tensors_nn_LazyConv3d_xpu_float32 case named in the report. Run the case repeatedly to investigate the intermittent Tensor-likes-are-not-close failure and compare the parameter gradients involved; done means the cause is understood and the test no longer fails nondeterministically.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, pytorch
Domain
machine-learning, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.