intel / intel/torch-xpu-ops

[Bug Skip]: New UT failure in 0406 nightly windows.

Open
#3,280 0 comments 0 reactions 0 assignees View on GitHub
skipped_windows
Dominant language
Python
Stars
113
Forks
128
Avg merge
5d 13h
Merged PRs (30d)
107

Description

### 🐛 Describe the bug with skip template

Cases:
op_extended,third_party.torch-xpu-ops.test.xpu.extended.test_ops_xpu.TestCommonXPU,test_compare_cpu_addcmul_xpu_int16
op_extended,third_party.torch-xpu-ops.test.xpu.extended.test_ops_xpu.TestCommonXPU,test_compare_cpu_addcmul_xpu_int32
op_extended,third_party.torch-xpu-ops.test.xpu.extended.test_ops_xpu.TestCommonXPU,test_compare_cpu_addcmul_xpu_int64
op_extended,third_party.torch-xpu-ops.test.xpu.extended.test_ops_xpu.TestCommonXPU,test_compare_cpu_addcmul_xpu_int8
op_extended,third_party.torch-xpu-ops.test.xpu.extended.test_ops_xpu.TestCommonXPU,test_compare_cpu_addcmul_xpu_uint8

### Versions

Log: https://github.com/intel/torch-xpu-ops/actions/runs/24034124139/job/70158521033

Contributor guide

Open the contributing guide

Research direction

Start with the GitHub Actions log for run 24034124139 and the five named test cases in third_party/torch-xpu-ops/test.xpu.extended.test_ops_xpu.TestCommonXPU. Determine why the int8, int16, int32, int64, and uint8 addcmul comparisons fail in the 0406 Windows nightly, then verify the appropriate test outcome in a subsequent run.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, pytorch
Domain
machine-learning, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.