The Graph/RecordReplay/usm_fill.cpp test has been observed to timeout in CUDA CI for unrelated changes. For example, see https://github.com/intel/llvm/pull/14985.
TIMEOUT: SYCL :: Graph/RecordReplay/usm_fill.cpp (1953 of 2130)
******************** TEST 'SYCL :: Graph/RecordReplay/usm_fill.cpp' FAILED ********************
Exit Code: -9
Timeout: Reached timeout of 600 seconds
Command Output (stdout):
--
# RUN: at line 1
.../llvm/toolchain/bin//clang++ -Werror -fsycl -fsycl-targets=nvptx64-nvidia-cuda .../llvm/llvm/sycl/test-e2e/Graph/RecordReplay/usm_fill.cpp -o .../llvm/build-e2e/Graph/RecordReplay/Output/usm_fill.cpp.tmp.out
# executed command: .../llvm/toolchain/bin//clang++ -Werror -fsycl -fsycl-targets=nvptx64-nvidia-cuda .../llvm/llvm/sycl/test-e2e/Graph/RecordReplay/usm_fill.cpp -o .../llvm/build-e2e/Graph/RecordReplay/Output/usm_fill.cpp.tmp.out
# note: command had no output on stdout or stderr
# RUN: at line 2
env SYCL_PI_CUDA_ENABLE_IMAGE_SUPPORT=1 ONEAPI_DEVICE_SELECTOR=cuda:gpu .../llvm/build-e2e/Graph/RecordReplay/Output/usm_fill.cpp.tmp.out
# executed command: env SYCL_PI_CUDA_ENABLE_IMAGE_SUPPORT=1 ONEAPI_DEVICE_SELECTOR=cuda:gpu .../llvm/build-e2e/Graph/RecordReplay/Output/usm_fill.cpp.tmp.out
# note: command had no output on stdout or stderr
# error: command failed with exit status: -9
# error: command reached timeout: True
--
To reproduce
Include a code snippet that is as short as possible
Specify the command which should be used to compile the program
Specify the command which should be used to launch the program
Indicate what is wrong and what was expected
Environment
OS: [e.g Windows/Linux]
Target device and vendor: [e.g. Intel GPU]
DPC++ version: [e.g. commit hash or output of clang++ --version]
Dependencies version: [e.g. the output of sycl-ls --verbose]
Describe the bug
The Graph/RecordReplay/usm_fill.cpp test has been observed to timeout in CUDA CI for unrelated changes. For example, see https://github.com/intel/llvm/pull/14985.
To reproduce
Environment
clang++ --version
]sycl-ls --verbose
]Additional context
No response