-
Notifications
You must be signed in to change notification settings - Fork 15.3k
Closed
Labels
Description
The test mapping/target_has_device_addr.c is failing on openmp-offload-cuda-runtime buildbot:
******************** TEST 'libomptarget :: nvptx64-nvidia-cuda :: mapping/target_has_device_addr.c' FAILED ********************
Script:
--
: 'RUN: at line 1'; /home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/./bin/clang -fopenmp -pthread --cuda-path=/opt/cuda -I /home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.src/openmp/libomptarget/test -I /home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/projects/openmp/runtime/src -L /home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/projects/openmp/libomptarget -L /home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/./lib -fno-openmp-implicit-rpath -Wl,-rpath,/home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/projects/openmp/libomptarget -Wl,-rpath,/home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/./lib -Wl,-rpath,/home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/./lib -Wl,-rpath,/opt/cuda/lib64 --libomptarget-nvptx-bc-path=/home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/projects/openmp/libomptarget -fopenmp-targets=nvptx64-nvidia-cuda /home/buildbot-worker/src/llvm-project/openmp/libomptarget/test/mapping/target_has_device_addr.c -o /home/buildbot-worker/minipc-1050ti-linux/openmp-offload-cuda-project/llvm.build/projects/openmp/libomptarget/test/nvptx64-nvidia-cuda/mapping/Output/target_has_device_addr.c.tmp -fopenmp-version=51
: 'RUN: at line 2'; /home/buildbot-worker/minipc-1050ti-linux/openmp-offload-cuda-project/llvm.build/projects/openmp/libomptarget/test/nvptx64-nvidia-cuda/mapping/Output/target_has_device_addr.c.tmp 2>&1 | /home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/./bin/FileCheck /home/buildbot-worker/src/llvm-project/openmp/libomptarget/test/mapping/target_has_device_addr.c
--
Exit Code: 1
Command Output (stdout):
--
$ ":" "RUN: at line 1"
$ "/home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/./bin/clang" "-fopenmp" "-pthread" "--cuda-path=/opt/cuda" "-I" "/home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.src/openmp/libomptarget/test" "-I" "/home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/projects/openmp/runtime/src" "-L" "/home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/projects/openmp/libomptarget" "-L" "/home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/./lib" "-fno-openmp-implicit-rpath" "-Wl,-rpath,/home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/projects/openmp/libomptarget" "-Wl,-rpath,/home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/./lib" "-Wl,-rpath,/home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/./lib" "-Wl,-rpath,/opt/cuda/lib64" "--libomptarget-nvptx-bc-path=/home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/projects/openmp/libomptarget" "-fopenmp-targets=nvptx64-nvidia-cuda" "/home/buildbot-worker/src/llvm-project/openmp/libomptarget/test/mapping/target_has_device_addr.c" "-o" "/home/buildbot-worker/minipc-1050ti-linux/openmp-offload-cuda-project/llvm.build/projects/openmp/libomptarget/test/nvptx64-nvidia-cuda/mapping/Output/target_has_device_addr.c.tmp" "-fopenmp-version=51"
$ ":" "RUN: at line 2"
$ "/home/buildbot-worker/minipc-1050ti-linux/openmp-offload-cuda-project/llvm.build/projects/openmp/libomptarget/test/nvptx64-nvidia-cuda/mapping/Output/target_has_device_addr.c.tmp"
note: command had no output on stdout or stderr
error: command failed with exit status: -6
$ "/home/buildbot-worker/minipc-1050ti-linux/rundir/llvm.build/./bin/FileCheck" "/home/buildbot-worker/src/llvm-project/openmp/libomptarget/test/mapping/target_has_device_addr.c"
# command stderr:
/home/buildbot-worker/src/llvm-project/openmp/libomptarget/test/mapping/target_has_device_addr.c:89:12: error: CHECK: expected string not found in input
// CHECK: 222 222
^
<stdin>:7:4: note: scanning from here
222 0x7ffff631ef30 0x7ffff631ef32
^
<stdin>:7:16: note: possible intended match here
222 0x7ffff631ef30 0x7ffff631ef32
^
Input file: <stdin>
Check file: /home/buildbot-worker/src/llvm-project/openmp/libomptarget/test/mapping/target_has_device_addr.c
-dump-input=help explains the following input dump.
Input was:
<<<<<<
1: Success
2: 222 0x7fcf44800602
3: 222 0x7ffff631ef32
4: 222 0x7fcf448007fe 0x7fcf44800800 0x7fcf419ff920
5: 222 0x55847488ce8e 0x55847488ce90 0x7ffff631ef48
6: 222 0x7fcf448007fe 0x7fcf44800800
7: 222 0x7ffff631ef30 0x7ffff631ef32
check:89'0 X~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ error: no match found
check:89'1 ? possible intended match
8: CUDA error: invalid argument
check:89'0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
9: Libomptarget error: Copying data to device failed.
check:89'0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10: Libomptarget error: Call to getTargetPointer returned null pointer (device failure or illegal mapping).
check:89'0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
11: Libomptarget error: Call to targetDataBegin failed, abort target.
check:89'0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
12: Libomptarget error: Failed to process data before launching the kernel.
check:89'0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.
.
.
>>>>>>
error: command failed with exit status: 1
--
********************