llvm-ci wrote:

LLVM Buildbot has detected a new failure on builder 
`clang-cmake-x86_64-avx512-linux` running on `avx512-intel64` while building 
`clang` at step 7 "ninja check 1".

Full details are available at: 
https://lab.llvm.org/buildbot/#/builders/133/builds/8646

<details>
<summary>Here is the relevant piece of the build log for the reference</summary>

```
Step 7 (ninja check 1) failure: stage 1 checked (failure)
******************** TEST 'Clang :: CodeGen/ubsan-trap-debugloc.c' FAILED 
********************
Exit Code: 1

Command Output (stderr):
--
RUN: at line 1: 
/localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/bin/clang
 -cc1 -internal-isystem 
/localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/lib/clang/20/include
 -nostdsysteminc -emit-llvm -disable-llvm-passes -O 
-fsanitize=signed-integer-overflow -fsanitize-trap=signed-integer-overflow 
/localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/clang/test/CodeGen/ubsan-trap-debugloc.c
 -o - -debug-info-kind=line-tables-only | 
/localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/bin/FileCheck
 
/localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/clang/test/CodeGen/ubsan-trap-debugloc.c
+ 
/localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/bin/clang
 -cc1 -internal-isystem 
/localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/lib/clang/20/include
 -nostdsysteminc -emit-llvm -disable-llvm-passes -O 
-fsanitize=signed-integer-overflow -fsanitize-trap=signed-integer-overflow 
/localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/clang/test/CodeGen/ubsan-trap-debugloc.c
 -o - -debug-info-kind=line-tables-only
+ 
/localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/bin/FileCheck
 
/localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/clang/test/CodeGen/ubsan-trap-debugloc.c
/localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/clang/test/CodeGen/ubsan-trap-debugloc.c:20:11:
 error: CHECK: expected string not found in input
// CHECK: [[LOC]] = !DILocation(line: 0
          ^
<stdin>:75:46: note: scanning from here
 call void @llvm.ubsantrap(i8 0) #4, !dbg !25, !nosanitize !8
                                             ^
<stdin>:75:46: note: with "LOC" equal to "!14"
 call void @llvm.ubsantrap(i8 0) #4, !dbg !25, !nosanitize !8
                                             ^
<stdin>:106:3: note: possible intended match here
!13 = !DILocation(line: 7, column: 7, scope: !5)
  ^

Input file: <stdin>
Check file: 
/localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/clang/test/CodeGen/ubsan-trap-debugloc.c

-dump-input=help explains the following input dump.

Input was:
<<<<<<
            .
            .
            .
           70:  %8 = extractvalue { i32, i1 } %6, 1, !dbg !25, !nosanitize !8 
           71:  %9 = xor i1 %8, true, !dbg !25, !nosanitize !8 
           72:  br i1 %9, label %cont2, label %trap1, !dbg !25, !nosanitize !8 
           73:  
           74: trap1: ; preds = %cont 
           75:  call void @llvm.ubsantrap(i8 0) #4, !dbg !25, !nosanitize !8 
check:20'0                                                  X~~~~~~~~~~~~~~~~ 
error: no match found
check:20'1                                                                    
with "LOC" equal to "!14"
           76:  unreachable, !dbg !25, !nosanitize !8 
check:20'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
           77:  
check:20'0     ~
           78: cont2: ; preds = %cont 
check:20'0     ~~~~~~~~~~~~~~~~~~~~~~~
           79:  store volatile i32 %7, ptr %a.addr, align 4, !dbg !26, !tbaa !9 
check:20'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
           80:  ret void, !dbg !27 
check:20'0     ~~~~~~~~~~~~~~~~~~~~
            .
...

```

</details>

https://github.com/llvm/llvm-project/pull/120464
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to