[clang] [llvm] [DebugInfo] Update DIBuilder insertion to take InsertPosition (PR #126059)
LLVM Continuous Integration via cfe-commits
cfe-commits at lists.llvm.org
Wed Feb 12 13:12:38 PST 2025
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `premerge-monolithic-linux` running on `premerge-linux-1` while building `clang,llvm` at step 7 "test-build-unified-tree-check-all".
Full details are available at: https://lab.llvm.org/buildbot/#/builders/153/builds/22689
<details>
<summary>Here is the relevant piece of the build log for the reference</summary>
```
Step 7 (test-build-unified-tree-check-all) failure: test (failure)
******************** TEST 'LLVM-Unit :: Frontend/./LLVMFrontendTests/3/81' FAILED ********************
Script(shard):
--
GTEST_OUTPUT=json:/build/buildbot/premerge-monolithic-linux/build/unittests/Frontend/./LLVMFrontendTests-LLVM-Unit-304124-3-81.json GTEST_SHUFFLE=0 GTEST_TOTAL_SHARDS=81 GTEST_SHARD_INDEX=3 /build/buildbot/premerge-monolithic-linux/build/unittests/Frontend/./LLVMFrontendTests
--
Note: This is test shard 4 of 81.
[==========] Running 2 tests from 2 test suites.
[----------] Global test environment set-up.
[----------] 1 test from OpenMPContextTest
[ RUN ] OpenMPContextTest.RoundTripAndAssociation
[ OK ] OpenMPContextTest.RoundTripAndAssociation (0 ms)
[----------] 1 test from OpenMPContextTest (0 ms total)
[----------] 1 test from OpenMPIRBuilderTest
[ RUN ] OpenMPIRBuilderTest.ConstantAllocaRaise
Basic Block has trailing DbgRecords!
label %entry
/build/buildbot/premerge-monolithic-linux/llvm-project/llvm/unittests/Frontend/OpenMPIRBuilderTest.cpp:6816: Failure
Value of: verifyModule(*M, &errs())
Actual: true
Expected: false
LLVMFrontendTests: /build/buildbot/premerge-monolithic-linux/llvm-project/llvm/lib/IR/LLVMContextImpl.cpp:50: llvm::LLVMContextImpl::~LLVMContextImpl(): Assertion `TrailingDbgRecords.empty() && "DbgRecords in blocks not cleaned"' failed.
Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it):
0 LLVMFrontendTests 0x00005647010de5c8
1 LLVMFrontendTests 0x00005647010dc50c
2 LLVMFrontendTests 0x00005647010ded91
3 libc.so.6 0x00007d6c2c3f2520
4 libc.so.6 0x00007d6c2c4469fc pthread_kill + 300
5 libc.so.6 0x00007d6c2c3f2476 raise + 22
6 libc.so.6 0x00007d6c2c3d87f3 abort + 211
7 libc.so.6 0x00007d6c2c3d871b
8 libc.so.6 0x00007d6c2c3e9e96
9 LLVMFrontendTests 0x0000564700f1b9e5
10 LLVMFrontendTests 0x0000564700f12161
11 LLVMFrontendTests 0x0000564700c5ec0d
12 LLVMFrontendTests 0x000056470112c50e
13 LLVMFrontendTests 0x000056470112d0a3
14 LLVMFrontendTests 0x000056470113de78
15 LLVMFrontendTests 0x000056470113d30c
16 LLVMFrontendTests 0x000056470111769c
17 libc.so.6 0x00007d6c2c3d9d90
18 libc.so.6 0x00007d6c2c3d9e40 __libc_start_main + 128
19 LLVMFrontendTests 0x0000564700b947c5
--
exit: -6
--
shard JSON output does not exist: /build/buildbot/premerge-monolithic-linux/build/unittests/Frontend/./LLVMFrontendTests-LLVM-Unit-304124-3-81.json
...
```
</details>
https://github.com/llvm/llvm-project/pull/126059
More information about the cfe-commits
mailing list