8000 Assertion Failure: TestMkldnnCPU.test_matmul_lower_precision_cpu_float16 on Graviton 2 & 3 · Issue #146484 · pytorch/pytorch · GitHub
[go: up one dir, main page]
Skip to content

Assertion Failure: TestMkldnnCPU.test_matmul_lower_precision_cpu_float16 on Graviton 2 & 3 #146484

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.

Sign up for GitHub

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

Jump to bottom
Closed
rahultrada opened this issue Feb 5, 2025 · 1 comment
Closed

Assertion Failure: TestMkldnnCPU.test_matmul_lower_precision_cpu_float16 on Graviton 2 & 3 #146484

rahultrada opened this issue Feb 5, 2025 · 1 comment
Labels
module: arm Related to ARM architectures builds of PyTorch. Includes Apple M1 module: correctness (silent) issue that returns an incorrect result silently module: mkldnn Related to Intel IDEEP or oneDNN (a.k.a. mkldnn) integration module: tests Issues related to tests (not the torch.testing module) triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module

Comments

@rahultrada
Copy link
rahultrada commented Feb 5, 2025 •
edited by pytorch-bot bot
Loading

🐛 Describe the bug

Repro

python test/test_mkldnn.py TestMkldnnCPU.test_matmul_lower_precision_cpu_float16

Error

File "/lib/python3.10/site-packages/torch/testing/_internal/common_utils.py", line 4042, in assertEqual
    raise error_metas.pop()[0].to_error(  # type: ignore[index]
AssertionError: Tensor-likes are not close!

Mismatched elements: 362 / 726 (49.9%)
Greatest absolute difference: 0.08086013793945312 at index (16, 6) (up to 1e-05 allowed)
Greatest relative difference: 0.16464824974536896 at index (19, 19) (up to 0.001 allowed)

To execute this test, run the following from the base repo dir:
    python test/test_mkldnn.py TestMkldnnCPU.test_matmul_lower_precision_cpu_float16

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0

This failure is not encountered in CI (on both Graviton 2 & 3).
This issue is possibly related to #146155, which is also a test failure not encountered in CI (although that issue only affected Graviton 3)

Versions

PyTorch version: 2.7.0.dev20250205+cpu
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.4 LTS (aarch64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: Could not collect
CMake version: version 3.22.1
Libc version: glibc-2.35

Python version: 3.10.12 (main, Jan 17 2025, 14:35:34) [GCC 11.4.0] (64-bit runtime)
Python platform: Linux-5.15.0-131-generic-aarch64-with-glibc2.35
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                         aarch64
CPU op-mode(s):                       32-bit, 64-bit
Byte Order:                           Little Endian
CPU(s):                               20
On-line CPU(s) list:                  0-19
Vendor ID:                            ARM
Model name:                           Neoverse-N1
Model:                                1
Thread(s) per core:                   1
Core(s) per socket:                   1
Socket(s):                            20
Stepping:                             r3p1
BogoMIPS:                             50.00
Flags:                                fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
NUMA node(s):                         1
NUMA node0 CPU(s):                    0-19
Vulnerability Gather data sampling:   Not affected
Vulnerability Itlb multihit:          Not affected
Vulnerability L1tf:                   Not affected
Vulnerability Mds:                    Not affected
Vulnerability Meltdown:               Not affected
Vulnerability Mmio stale data:        Not affected
Vulnerability Reg file data sampling: Not affected
Vulnerability Retbleed:               Not affected
Vulnerability Spec rstack overflow:   Not affected
Vulnerability Spec store bypass:      Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:             Mitigation; __user pointer sanitization
Vulnerability Spectre v2:             Mitigation; CSV2, BHB
Vulnerability Srbds:                  Not affected
Vulnerability Tsx async abort:        Not affected

Versions of relevant libraries:
[pip3] numpy==2.2.2
[pip3] torch==2.7.0.dev20250205+cpu
[conda] Could not collect

cc @mruberry @ZainRizvi @gujinghui @PenghuiCheng @XiaobingSuper @jianyuh @jgong5 @mingfeima @sanchitintel @ashokei @jingxu10 @min-jean-cho @yanbing-j @Guobing-Chen @Xia-Weiwen @snadampal @malfet @milpuz01
9D49
@malfet malfet added module: tests Issues related to tests (not the torch.testing module) triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module module: mkldnn Related to Intel IDEEP or oneDNN (a.k.a. mkldnn) integration module: correctness (silent) issue that returns an incorrect result silently module: arm Related to ARM architectures builds of PyTorch. Includes Apple M1 labels Feb 5, 2025
@fadara01
Copy link
Collaborator
fadara01 commented May 23, 2025 •
edited
Loading

This test failed due to #144992 which got reverted, so the test should be passing now in both manylinux wheels and CI.

Please refer to this comment which explains why this test did not fail in CI and why the reverted PR triggered the failures.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
module: arm Related to ARM architectures builds of PyTorch. Includes Apple M1 module: correctness (silent) issue that returns an incorrect result silently module: mkldnn Related to Intel IDEEP or oneDNN (a.k.a. mkldnn) integration module: tests Issues related to tests (not the torch.testing module) triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@malfet @rahultrada @fadara01
0