8000 Assertion Failure: TestBinaryUfuncsCPU.test_lerp_cpu_complex64 on Graviton 3 · Issue #146155 · pytorch/pytorch · GitHub
[go: up one dir, main page]
Skip to content

Assertion Failure: TestBinaryUfuncsCPU.test_lerp_cpu_complex64 on Graviton 3 #146155

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
Open
kundaMwiza opened this issue Jan 31, 2025 · 1 comment
Open

Assertion Failure: TestBinaryUfuncsCPU.test_lerp_cpu_complex64 on Graviton 3 #146155

kundaMwiza opened this issue Jan 31, 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: cpu CPU specific problem (e.g., perf, algorithm) 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

@kundaMwiza
Copy link
Contributor
kundaMwiza commented Jan 31, 2025 •
edited by pytorch-bot bot
Loading

🐛 Describe the bug

Repro:

python test/test_binary_ufuncs.py TestBinaryUfuncsCPU.test_lerp_cpu_complex64

Error:

Traceback (most recent call last): 

in test_lerp self.assertEqual(expected, actual) File "/lib/python3.10/site-packages/torch/testing/_internal/common_utils.py", line 4036, in assertEqual raise error_metas.pop()[0].to_error( # type: ignore[index] AssertionError: Tensor-likes are not close! Mismatched elements: 1 / 5 (20.0%) Greatest absolute difference: 0.2975790798664093 at index (2,) (up to 1e-05 allowed) Greatest relative difference: 0.1535184681415558 at index (2,) (up to 1.3e-06 allowed) To execute this test, run the following from the base repo dir: python test/test_binary_ufuncs.py TestBinaryUfuncsCPU.test_lerp_cpu_complex64 This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0

This failure is currently not encountered in CI, see #146153

Versions

PyTorch version: 2.7.0a0+git367593d
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.5 LTS (aarch64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: Could not collect
CMake version: version 3.31.4
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-6.8.0-1021-aws-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):                               16
On-line CPU(s) list:                  0-15
Vendor ID:                            ARM
Model:                                1
Thread(s) per core:                   1
Core(s) per socket:                   16
Socket(s):                            1
Stepping:                             r1p1
BogoMIPS:                             2100.00
Flags:                                fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm dit uscat ilrcpc flagm ssbs paca pacg dcpodp svei8mm svebf16 i8mm bf16 dgh rng
L1d cache:                            1 MiB (16 instances)
L1i cache:                            1 MiB (16 instances)
L2 cache:                             16 MiB (16 instances)
L3 cache:                             32 MiB (1 instance)
NUMA node(s):                         1
NUMA node0 CPU(s):                    0-15
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] mypy==1.13.0
[pip3] mypy-extensions==1.0.0
[pip3] numpy==2.2.2
[pip3] onnx==1.17.0
[pip3] onnxscript==0.1.0.dev20240817
[pip3] optree==0.14.0
[pip3] torch==2.7.0a0+git367593d

cc @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10 @mruberry @ZainRizvi @malfet @snadampal @milpuz01
@malfet malfet added module: tests Issues related to tests (not the torch.testing module) module: arm Related to ARM architectures builds of PyTorch. Includes Apple M1 module: correctness (silent) issue that returns an incorrect result silently module: cpu CPU specific problem (e.g., perf, algorithm) triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module labels Jan 31, 2025
@rahultrada rahultrada mentioned this issue Feb 5, 2025
Open
@rahultrada
Copy link

Note this test is no longer failing on 2.8.0.dev20250511

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: cpu CPU specific problem (e.g., perf, algorithm) 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 @kundaMwiza @rahultrada
0