3 llvm-test-suite tests failed on GPU with PI CUDA error after pulldown from LLORG

[vmaksimo]

3 LLVM test suite tests started to fail on CUDA GPU after LLORG pulldown (#4054). They are temporarily disabled by intel/llvm-test-suite#349 to unlock the pulldown process.

List of failed tests:

SYCL :: Basic/multisource.cpp, 
SYCL :: SeparateCompile/same-kernel.cpp,
SYCL :: SeparateCompile/sycl-external.cpp

Failure log:

PI CUDA ERROR:
	Value:           500
	Name:            CUDA_ERROR_NOT_FOUND
	Description:     named symbol not found
	Function:        cuda_piKernelCreate
	Source Location: sycl/plugins/cuda/pi_cuda.cpp:2299

terminate called after throwing an instance of 'cl::sycl::runtime_error'
  what():  Native API failed. Native API returns: -999 (Unknown OpenCL error code) -999 (Unknown OpenCL error code)

error: command failed with exit status: -6

To Reproduce

# If the https://github.com/intel/llvm/pull/4054 is not merged yet, fetch the PR:
git fetch origin pull/4054 /head:pr_4054
git checkout pr_4054 
# Otherwise, please checkout the latest sycl branch

# Then build with the normal procedure https://github.com/intel/llvm/blob/sycl/sycl/doc/GetStartedGuide.md#build-dpc-toolchain
python $DPCPP_HOME/llvm/buildbot/configure.py
python $DPCPP_HOME/llvm/buildbot/compile.py

# Get sources of intel/llvm-test-suite
git clone https://github.com/intel/llvm-test-suite

# Then revert the commit that disables the test
# See the hash in PR: https://github.com/intel/llvm-test-suite/pull/349
git revert <hash_placeholder>

# Then build intel/llvm-test-suite per normal procedure
# https://github.com/intel/llvm-test-suite/tree/intel/SYCL#build-and-run-tests

Environment (please complete the following information):

• OS: Linux
• Target device and vendor: CUDA

[steffenlarsen]

Thanks for the detailed report! This problem with #4112 and the corresponding tests are re-enabled for CUDA with intel/llvm-test-suite#365.

[bader]

@steffenlarsen, does #4112 resolves #4088 as well?

[steffenlarsen]

@steffenlarsen, does #4112 resolves #4088 as well?

I believe so, but I will have to test it.

[steffenlarsen]

@bader I can confirm that #4112 seems to resolve #4088 .