UltimateForce21 wrote: I just wanted to provide an update on the CI failures:
I reverted the branch back to commit e5e168f (which previously passed all Linux Build Tests) and force-pushed, but the same LLDB data formatter tests are still failing in the current workflow run. Based on this, I don’t think the failures are caused by my changes in this PR — they look unrelated and might be coming from upstream. Specifically, the failures are in the `lldb-api.functionalities/data-formatter/data-formatter-stl` suite (`forward_list`, `list`, and `list/loop tests`). These tests were not failing when e5e168f originally landed, but they now consistently fail even after rolling the branch back to that known-good commit. It seems like a regression or flakiness at HEAD, rather than something introduced by this PR. Please let me know if you’d like me to open an issue on GitHub with the logs under the infrastructure label, as the failure message suggests. https://github.com/llvm/llvm-project/pull/152887 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
