Skip to content
This repository was archived by the owner on Mar 28, 2023. It is now read-only.

[SYCL] E2E test for interop_task with Level-Zero using get_mem() #168

Merged
merged 1 commit into from
May 19, 2021

Conversation

smaslov-intel
Copy link

@smaslov-intel smaslov-intel commented Mar 4, 2021

Compiler support is coming in intel/llvm#3307
Signed-off-by: Sergey V Maslov [email protected]

@vladimirlaz
Copy link

@againull could you please fix the issue SYCL :: Plugin/interop-level-zero-interop-task-mem.cpp?

@smaslov-intel
Copy link
Author

@vladimirlaz , what is the compiler used in this E2E testing? The compiler fix was merged long ago, but it still looks like the fail is because of not using the right compiler.

@vladimirlaz
Copy link

vladimirlaz commented Mar 9, 2021

the latest available nightly from intel/llvm. @hanzhan1, @tfzhu could you please check and confirm, that the latest nightly is used?

@smaslov-intel
Copy link
Author

I cannot reproduce it with ToT:

$ "env" "SYCL_BE=PI_LEVEL_ZERO" "env" "SYCL_DEVICE_FILTER=level_zero:gpu" ./a.out

WARNING: The legacy environment variables SYCL_BE and SYCL_DEVICE_TYPE are deprecated. Please use SYCL_DEVICE_FILTER instead. For details, please refer to https://github.com/intel/llvm/blob/sycl/sycl/doc/EnvironmentVariables.md

zeContextGetStatus = 0
Memory type = 1

@hanzhan1
Copy link

According to the log, pre-ci-linux used latest nightly version b1e1de06fdf8b9fa9b536e731f888bb6cd4f82be of date stamp 20210309_160000.

@smaslov-intel
Copy link
Author

@vladimirlaz : the test is taken as is from a customer. Adding waits/catches/etc may cause completely different behavior so I don't think we need to beatify the tests.

@vladimirlaz
Copy link

@vladimirlaz : the test is taken as is from a customer. Adding waits/catches/etc may cause completely different behavior so I don't think we need to beatify the tests.

we need to be sure that the test is stable enough to use in regular testing. It should not be submitted if it is flaky or fails on some platforms.

@smaslov-intel
Copy link
Author

I agree, we should not add flaky tests for sure. Are you seeing flaky behavior in the test? The only fail that I see currently is stable:


[2021-03-16T05:55:48.918Z] ******************** TEST 'SYCL :: Plugin/interop-level-zero-interop-task-mem.cpp' FAILED ********************
[2021-03-16T05:55:48.918Z] Script:
[2021-03-16T05:55:48.918Z] --
[2021-03-16T05:55:48.918Z] : 'RUN: at line 2';    /localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm.obj/bin/clang++     -fsycl -fsycl-targets=spir64-unknown-unknown-sycldevice  -lze_loader  -I/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm.obj/include/sycl/.. /localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm-test-suite/SYCL/Plugin/interop-level-zero-interop-task-mem.cpp -o /localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/build/SYCL/Plugin/Output/interop-level-zero-interop-task-mem.cpp.tmp.out
[2021-03-16T05:55:48.918Z] : 'RUN: at line 3';    env SYCL_DEVICE_FILTER=level_zero:gpu  /localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/build/SYCL/Plugin/Output/interop-level-zero-interop-task-mem.cpp.tmp.out
[2021-03-16T05:55:48.918Z] --
[2021-03-16T05:55:48.918Z] Exit Code: -6
[2021-03-16T05:55:48.918Z] 
[2021-03-16T05:55:48.918Z] Command Output (stdout):
[2021-03-16T05:55:48.918Z] --
[2021-03-16T05:55:48.918Z] $ ":" "RUN: at line 2"
[2021-03-16T05:55:48.918Z] note: command had no output on stdout or stderr
[2021-03-16T05:55:48.918Z] $ "/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm.obj/bin/clang++" "-fsycl" "-fsycl-targets=spir64-unknown-unknown-sycldevice" "-lze_loader" "-I/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm.obj/include/sycl/.." "/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm-test-suite/SYCL/Plugin/interop-level-zero-interop-task-mem.cpp" "-o" "/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/build/SYCL/Plugin/Output/interop-level-zero-interop-task-mem.cpp.tmp.out"
[2021-03-16T05:55:48.918Z] note: command had no output on stdout or stderr
[2021-03-16T05:55:48.918Z] $ ":" "RUN: at line 3"
[2021-03-16T05:55:48.918Z] note: command had no output on stdout or stderr
[2021-03-16T05:55:48.918Z] $ "env" "SYCL_DEVICE_FILTER=level_zero:gpu" "/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/build/SYCL/Plugin/Output/interop-level-zero-interop-task-mem.cpp.tmp.out"
[2021-03-16T05:55:48.918Z] # command output:
[2021-03-16T05:55:48.918Z] zeContextGetStatus = 0
[2021-03-16T05:55:48.918Z] 
[2021-03-16T05:55:48.918Z] # command stderr:
[2021-03-16T05:55:48.918Z] terminate called after throwing an instance of 'char const*'
[2021-03-16T05:55:48.918Z] 
[2021-03-16T05:55:48.918Z] error: command failed with exit status: -6

BUT I cannot reproduce it locally. Any suggestions?

@vladimirlaz
Copy link

I agree, we should not add flaky tests for sure. Are you seeing flaky behavior in the test? The only fail that I see currently is stable:


[2021-03-16T05:55:48.918Z] ******************** TEST 'SYCL :: Plugin/interop-level-zero-interop-task-mem.cpp' FAILED ********************
[2021-03-16T05:55:48.918Z] Script:
[2021-03-16T05:55:48.918Z] --
[2021-03-16T05:55:48.918Z] : 'RUN: at line 2';    /localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm.obj/bin/clang++     -fsycl -fsycl-targets=spir64-unknown-unknown-sycldevice  -lze_loader  -I/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm.obj/include/sycl/.. /localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm-test-suite/SYCL/Plugin/interop-level-zero-interop-task-mem.cpp -o /localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/build/SYCL/Plugin/Output/interop-level-zero-interop-task-mem.cpp.tmp.out
[2021-03-16T05:55:48.918Z] : 'RUN: at line 3';    env SYCL_DEVICE_FILTER=level_zero:gpu  /localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/build/SYCL/Plugin/Output/interop-level-zero-interop-task-mem.cpp.tmp.out
[2021-03-16T05:55:48.918Z] --
[2021-03-16T05:55:48.918Z] Exit Code: -6
[2021-03-16T05:55:48.918Z] 
[2021-03-16T05:55:48.918Z] Command Output (stdout):
[2021-03-16T05:55:48.918Z] --
[2021-03-16T05:55:48.918Z] $ ":" "RUN: at line 2"
[2021-03-16T05:55:48.918Z] note: command had no output on stdout or stderr
[2021-03-16T05:55:48.918Z] $ "/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm.obj/bin/clang++" "-fsycl" "-fsycl-targets=spir64-unknown-unknown-sycldevice" "-lze_loader" "-I/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm.obj/include/sycl/.." "/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm-test-suite/SYCL/Plugin/interop-level-zero-interop-task-mem.cpp" "-o" "/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/build/SYCL/Plugin/Output/interop-level-zero-interop-task-mem.cpp.tmp.out"
[2021-03-16T05:55:48.918Z] note: command had no output on stdout or stderr
[2021-03-16T05:55:48.918Z] $ ":" "RUN: at line 3"
[2021-03-16T05:55:48.918Z] note: command had no output on stdout or stderr
[2021-03-16T05:55:48.918Z] $ "env" "SYCL_DEVICE_FILTER=level_zero:gpu" "/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/build/SYCL/Plugin/Output/interop-level-zero-interop-task-mem.cpp.tmp.out"
[2021-03-16T05:55:48.918Z] # command output:
[2021-03-16T05:55:48.918Z] zeContextGetStatus = 0
[2021-03-16T05:55:48.918Z] 
[2021-03-16T05:55:48.918Z] # command stderr:
[2021-03-16T05:55:48.918Z] terminate called after throwing an instance of 'char const*'
[2021-03-16T05:55:48.918Z] 
[2021-03-16T05:55:48.918Z] error: command failed with exit status: -6

BUT I cannot reproduce it locally. Any suggestions?

I agree, we should not add flaky tests for sure. Are you seeing flaky behavior in the test? The only fail that I see currently is stable:


[2021-03-16T05:55:48.918Z] ******************** TEST 'SYCL :: Plugin/interop-level-zero-interop-task-mem.cpp' FAILED ********************
[2021-03-16T05:55:48.918Z] Script:
[2021-03-16T05:55:48.918Z] --
[2021-03-16T05:55:48.918Z] : 'RUN: at line 2';    /localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm.obj/bin/clang++     -fsycl -fsycl-targets=spir64-unknown-unknown-sycldevice  -lze_loader  -I/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm.obj/include/sycl/.. /localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm-test-suite/SYCL/Plugin/interop-level-zero-interop-task-mem.cpp -o /localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/build/SYCL/Plugin/Output/interop-level-zero-interop-task-mem.cpp.tmp.out
[2021-03-16T05:55:48.918Z] : 'RUN: at line 3';    env SYCL_DEVICE_FILTER=level_zero:gpu  /localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/build/SYCL/Plugin/Output/interop-level-zero-interop-task-mem.cpp.tmp.out
[2021-03-16T05:55:48.918Z] --
[2021-03-16T05:55:48.918Z] Exit Code: -6
[2021-03-16T05:55:48.918Z] 
[2021-03-16T05:55:48.918Z] Command Output (stdout):
[2021-03-16T05:55:48.918Z] --
[2021-03-16T05:55:48.918Z] $ ":" "RUN: at line 2"
[2021-03-16T05:55:48.918Z] note: command had no output on stdout or stderr
[2021-03-16T05:55:48.918Z] $ "/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm.obj/bin/clang++" "-fsycl" "-fsycl-targets=spir64-unknown-unknown-sycldevice" "-lze_loader" "-I/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm.obj/include/sycl/.." "/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/llvm-test-suite/SYCL/Plugin/interop-level-zero-interop-task-mem.cpp" "-o" "/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/build/SYCL/Plugin/Output/interop-level-zero-interop-task-mem.cpp.tmp.out"
[2021-03-16T05:55:48.918Z] note: command had no output on stdout or stderr
[2021-03-16T05:55:48.918Z] $ ":" "RUN: at line 3"
[2021-03-16T05:55:48.918Z] note: command had no output on stdout or stderr
[2021-03-16T05:55:48.918Z] $ "env" "SYCL_DEVICE_FILTER=level_zero:gpu" "/localdisk2/llvm-test-suite_Jenkins/workspace/LLVM-Test-Suite-CI/LLVM-Test-Suite-Lin/build/SYCL/Plugin/Output/interop-level-zero-interop-task-mem.cpp.tmp.out"
[2021-03-16T05:55:48.918Z] # command output:
[2021-03-16T05:55:48.918Z] zeContextGetStatus = 0
[2021-03-16T05:55:48.918Z] 
[2021-03-16T05:55:48.918Z] # command stderr:
[2021-03-16T05:55:48.918Z] terminate called after throwing an instance of 'char const*'
[2021-03-16T05:55:48.918Z] 
[2021-03-16T05:55:48.918Z] error: command failed with exit status: -6

BUT I cannot reproduce it locally. Any suggestions?

According to logs it looks like char* string was thrown. Adding try/catch wrapper does not affect the code but helps to analyze failures.

@bader
Copy link

bader commented Mar 26, 2021

@smaslov-intel, do you have updates for this PR?

@vladimirlaz
Copy link

@smaslov-intel, Is this PR still needed?

@smaslov-intel smaslov-intel changed the title [SYCL] E2E test fot interop_task with Level-Zero using get_mem() [SYCL] E2E test for interop_task with Level-Zero using get_mem() May 17, 2021
@smaslov-intel
Copy link
Author

@smaslov-intel, Is this PR still needed?

Yes. I can't reproduce the reported fail locally. How to restart the Jenkins testing?

@vladimirlaz
Copy link

@smaslov-intel, I have restarted testing.

vladimirlaz
vladimirlaz previously approved these changes May 18, 2021
@smaslov-intel
Copy link
Author

[2021-05-19T00:20:56.729Z] New failures found: ['SYCL::Basic/half_type.cpp', 'SYCL::Basic/reqd_work_group_size.cpp', 'SYCL::Functor/kernel_functor.cpp', 'SYCL::Plugin/interop-level-zero-interop-task-mem.cpp', 'SYCL::Reduction/reduction_queue_parallel_for.cpp', 'SYCL::Reduction/reduction_nd_s0_rw.cpp', 'SYCL::USM/memset.cpp']

@vladimirlaz : I have no clue how to proceed with this.

  1. The test I am adding passes locally: interop-level-zero-interop-task-mem.cpp
  2. Six other tests are showing as new fails, although I didn't touch them.

Any idea?

@vladimirlaz
Copy link

The same tests are failing for other PRs.

@vladimirlaz vladimirlaz merged commit 29b4273 into intel:intel May 19, 2021
@smaslov-intel
Copy link
Author

The same tests are failing for other PRs.

Does it mean they are real fails that need to be analyzed/fixed?
Why are they showing as "new failures"?

@bader
Copy link

bader commented May 19, 2021

Please, keep 0 failing tests.

@vladimirlaz
Copy link

This is environment issue which is under analysis by tools guys.

aelovikov-intel pushed a commit to aelovikov-intel/llvm that referenced this pull request Mar 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants