intel / intel/llvm

SYCL :: atomic_memory_order_seq_cst.cpp timeout on DG2 Windows

Open
#22,703 0 comments 0 reactions 0 assignees View on GitHub
bug unified-runtime
Dominant language
LLVM
Stars
1.5k
Forks
854
Avg merge
3d 17h
Merged PRs (30d)
137

Description

### Describe the bug

"https://raw.githubusercontent.com/intel/llvm/refs/heads/sycl/devops/scripts/windows_detect_hung_tests.ps1" -OutFile "windows_detect_hung_tests.ps1" -Headers @{Authorization = "***"}
Test d:\github\_work\llvm\llvm\build-e2e\atomicref\output\atomic_memory_order_seq_cst.cpp.tmp.out hung!
Error: Process completed with exit code 1.

https://github.com/intel/llvm/actions/runs/29594821764/job/88654812279?pr=22661

### Environment

- OS: Windows
- Target device and vendor: Intel Arc Graphics with Level Zero

Contributor guide

Open the contributing guide

Research direction

Start with the linked GitHub Actions job and the failing atomic_memory_order_seq_cst.cpp test output. Read windows_detect_hung_tests.ps1 to understand how the hang is detected, then reproduce the timeout on Windows with an Intel Arc DG2 device using Level Zero. Done means the test completes successfully without being reported as hung.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
operating-systems, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.