Skip to content
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.

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

syclcompat/memory/memory_async.cpp failed in post-commit #13636

Closed
KornevNikita opened this issue May 2, 2024 · 3 comments
Closed

syclcompat/memory/memory_async.cpp failed in post-commit #13636

KornevNikita opened this issue May 2, 2024 · 3 comments
Labels
bug Something isn't working confirmed syclcompat Issues related to SYCLcompat

Comments

@KornevNikita
Copy link
Contributor

Describe the bug

see: https://github.com/intel/llvm/actions/runs/8921355161/job/24501752365?pr=13601

FAIL: SYCL :: syclcompat/memory/memory_async.cpp (2007 of 2020)
******************** TEST 'SYCL :: syclcompat/memory/memory_async.cpp' FAILED ********************
Exit Code: -11

Command Output (stdout):
--
# RUN: at line 33
/__w/llvm/llvm/toolchain/bin//clang++   -std=c++20 -fsycl -fsycl-targets=spir64 /__w/llvm/llvm/llvm/sycl/test-e2e/syclcompat/memory/memory_async.cpp -o /__w/llvm/llvm/build-e2e/syclcompat/memory/Output/memory_async.cpp.tmp.out
# executed command: /__w/llvm/llvm/toolchain/bin//clang++ -std=c++20 -fsycl -fsycl-targets=spir64 /__w/llvm/llvm/llvm/sycl/test-e2e/syclcompat/memory/memory_async.cpp -o /__w/llvm/llvm/build-e2e/syclcompat/memory/Output/memory_async.cpp.tmp.out
# .---command stderr------------
# | In file included from /__w/llvm/llvm/llvm/sycl/test-e2e/syclcompat/memory/memory_async.cpp:42:
# | In file included from /__w/llvm/llvm/toolchain/bin/../include/syclcompat/memory.hpp:53:
# | /__w/llvm/llvm/toolchain/bin/../include/syclcompat/device.hpp:348:2: warning: "Querying the number of bytes of free memory is not supported" [-W#warnings]
# |   348 | #warning "Querying the number of bytes of free memory is not supported"
# |       |  ^
# | 1 warning generated.
# | In file included from /__w/llvm/llvm/llvm/sycl/test-e2e/syclcompat/memory/memory_async.cpp:42:
# | In file included from /__w/llvm/llvm/toolchain/bin/../include/syclcompat/memory.hpp:53:
# | /__w/llvm/llvm/toolchain/bin/../include/syclcompat/device.hpp:348:2: warning: "Querying the number of bytes of free memory is not supported" [-W#warnings]
# |   348 | #warning "Querying the number of bytes of free memory is not supported"
# |       |  ^
# | /__w/llvm/llvm/toolchain/bin/../include/syclcompat/device.hpp:406:2: warning: "get_device_info: querying memory_clock_rate and memory_bus_width are not supported by the compiler used. Use [32](https://github.com/intel/llvm/actions/runs/8921355161/job/24501752365?pr=13601#step:21:33)00000 kHz as memory_clock_rate default value. Use 64 bits as memory_bus_width default value." [-W#warnings]
# |   406 | #warning "get_device_info: querying memory_clock_rate and \
# |       |  ^
# | 2 warnings generated.
# `-----------------------------
# RUN: at line [34](https://github.com/intel/llvm/actions/runs/8921355161/job/24501752365?pr=13601#step:21:35)
env ONEAPI_DEVICE_SELECTOR=level_zero:gpu  /__w/llvm/llvm/build-e2e/syclcompat/memory/Output/memory_async.cpp.tmp.out
# executed command: env ONEAPI_DEVICE_SELECTOR=level_zero:gpu /__w/llvm/llvm/build-e2e/syclcompat/memory/Output/memory_async.cpp.tmp.out
# .---command stdout------------
# | void test_free_async()
# | void test_memcpy_async1()
# | void test_memcpy_async2()
# | void test_memcpy_async3()
# | void test_memset_async1()
# `-----------------------------
# error: command failed with exit status: -11

To reproduce

No response

Environment

No response

Additional context

No response

@KornevNikita KornevNikita added bug Something isn't working confirmed labels May 2, 2024
@Alcpz Alcpz added the syclcompat Issues related to SYCLcompat label May 2, 2024
@Alcpz
Copy link
Contributor

Alcpz commented May 2, 2024

I had a flaky test a day ago for level_zero as well, but it was a different test. So far I haven't been able to reproduce the issue. We will have a deeper look into this.

@joeatodd ping for visibility.

@joeatodd
Copy link
Contributor

joeatodd commented May 3, 2024

We've been investigating this. None of these tests have been touched recently, so I expect we are exposing an issue in UR or L0. I've been unable to reproduce the failure locally on our Arc A770.

It also seems like the failure has stopped occurring 🤞 though given it's intermittent we can't yet be sure.

For now I'd suggest we wait and see if it continues to occur. If so we will need to look deeper.

@joeatodd
Copy link
Contributor

I have been intermittently checking recent SYCL Post Commit actions and this failure hasn't re-occurred for a couple of weeks now. We believe we were probably exposing an underlying L0 bug which has likely since been resolved. Closing this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working confirmed syclcompat Issues related to SYCLcompat
Projects
None yet
Development

No branches or pull requests

3 participants