| Issue |
154763
|
| Summary |
[CI][lldb] Flaky tests
|
| Labels |
new issue
|
| Assignees |
boomanaiden154
|
| Reporter |
boomanaiden154
|
We're seeing a significant number of CI flakes (3/~50 runs have failed).
1. https://lab.llvm.org/staging/#/builders/192/builds/1291
2. https://lab.llvm.org/staging/#/builders/192/builds/1295
3. https://lab.llvm.org/staging/#/builders/192/builds/1325
One shows the following failed test:
```
2025-08-21T06:51:18.635834216Z ********************
2025-08-21T06:51:18.635836396Z Failed Tests (1):
2025-08-21T06:51:18.635838606Z lldb-unit :: DAP/./DAPTests/DisconnectRequestHandlerTest/DisconnectTriggersTerminateCommands
```
Two fail to resolve the following test:
```
2025-08-21T13:00:19.674647238Z ********************
2025-08-21T13:00:19.674650118Z Unresolved Tests (1):
2025-08-21T13:00:19.674653028Z lldb-api :: functionalities/statusline/TestStatusline.py
```
This is on the premerge buildbot, but I assume these are showing up premerge as well given the configuration is almost exactly the same (same shell script running in the same container on the same cluster). This makes changes like d9d5090b03f71e5be303b858a89b0ec93c1cb270 a lot harder to justify given many more people now need to pay the price of flaky tests.
![]()
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
