We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
See: https://github.com/intel/llvm/actions/runs/8751296542/job/24017031750?pr=13421 Output:
FAIL: SYCL :: Graph/Explicit/assume_buffer_outlives_graph_property.cpp (918 of 1987) ******************** TEST 'SYCL :: Graph/Explicit/assume_buffer_outlives_graph_property.cpp' FAILED ******************** Exit Code: -6 Command Output (stdout): -- # RUN: at line 1 /__w/llvm/llvm/toolchain/bin//clang++ -fsycl -fsycl-targets=spir64 /__w/llvm/llvm/llvm/sycl/test-e2e/Graph/Explicit/assume_buffer_outlives_graph_property.cpp -o /__w/llvm/llvm/build-e2e/Graph/Explicit/Output/assume_buffer_outlives_graph_property.cpp.tmp.out # executed command: /__w/llvm/llvm/toolchain/bin//clang++ -fsycl -fsycl-targets=spir64 /__w/llvm/llvm/llvm/sycl/test-e2e/Graph/Explicit/assume_buffer_outlives_graph_property.cpp -o /__w/llvm/llvm/build-e2e/Graph/Explicit/Output/assume_buffer_outlives_graph_property.cpp.tmp.out # note: command had no output on stdout or stderr # RUN: at line 2 env ONEAPI_DEVICE_SELECTOR=level_zero:gpu /__w/llvm/llvm/build-e2e/Graph/Explicit/Output/assume_buffer_outlives_graph_property.cpp.tmp.out # executed command: env ONEAPI_DEVICE_SELECTOR=level_zero:gpu /__w/llvm/llvm/build-e2e/Graph/Explicit/Output/assume_buffer_outlives_graph_property.cpp.tmp.out # note: command had no output on stdout or stderr # RUN: at line 4 env SYCL_PI_LEVEL_ZERO_USE_IMMEDIATE_COMMANDLISTS=0 env UR_L0_LEAKS_DEBUG=1 env ONEAPI_DEVICE_SELECTOR=level_zero:gpu /__w/llvm/llvm/build-e2e/Graph/Explicit/Output/assume_buffer_outlives_graph_property.cpp.tmp.out 2>&1 | /__w/llvm/llvm/toolchain/bin/FileCheck /__w/llvm/llvm/llvm/sycl/test-e2e/Graph/Explicit/assume_buffer_outlives_graph_property.cpp --implicit-check-not=LEAK # executed command: env SYCL_PI_LEVEL_ZERO_USE_IMMEDIATE_COMMANDLISTS=0 env UR_L0_LEAKS_DEBUG=1 env ONEAPI_DEVICE_SELECTOR=level_zero:gpu /__w/llvm/llvm/build-e2e/Graph/Explicit/Output/assume_buffer_outlives_graph_property.cpp.tmp.out # note: command had no output on stdout or stderr # executed command: /__w/llvm/llvm/toolchain/bin/FileCheck /__w/llvm/llvm/llvm/sycl/test-e2e/Graph/Explicit/assume_buffer_outlives_graph_property.cpp --implicit-check-not=LEAK # note: command had no output on stdout or stderr # RUN: at line 6 env SYCL_PI_LEVEL_ZERO_USE_IMMEDIATE_COMMANDLISTS=1 env UR_L0_LEAKS_DEBUG=1 env ONEAPI_DEVICE_SELECTOR=level_zero:gpu /__w/llvm/llvm/build-e2e/Graph/Explicit/Output/assume_buffer_outlives_graph_property.cpp.tmp.out 2>&1 | /__w/llvm/llvm/toolchain/bin/FileCheck /__w/llvm/llvm/llvm/sycl/test-e2e/Graph/Explicit/assume_buffer_outlives_graph_property.cpp --implicit-check-not=LEAK # executed command: env SYCL_PI_LEVEL_ZERO_USE_IMMEDIATE_COMMANDLISTS=1 env UR_L0_LEAKS_DEBUG=1 env ONEAPI_DEVICE_SELECTOR=level_zero:gpu /__w/llvm/llvm/build-e2e/Graph/Explicit/Output/assume_buffer_outlives_graph_property.cpp.tmp.out # note: command had no output on stdout or stderr # error: command failed with exit status: -6 # executed command: /__w/llvm/llvm/toolchain/bin/FileCheck /__w/llvm/llvm/llvm/sycl/test-e2e/Graph/Explicit/assume_buffer_outlives_graph_property.cpp --implicit-check-not=LEAK # note: command had no output on stdout or stderr --
No response
The text was updated successfully, but these errors were encountered:
I don't see it in another runs, must be flaky.
Sorry, something went wrong.
This looks like it's related to #13301 as the linked fail is on Arc
Test should now be disabled by #13561 until we can understand and fix the root cause
No branches or pull requests
Describe the bug
See: https://github.com/intel/llvm/actions/runs/8751296542/job/24017031750?pr=13421
Output:
To reproduce
No response
Environment
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: