Author: David Spickett Date: 2025-06-13T09:12:01Z New Revision: 06c783567069db169ee2d1545a4bd3ffd0e3fec0
URL: https://github.com/llvm/llvm-project/commit/06c783567069db169ee2d1545a4bd3ffd0e3fec0 DIFF: https://github.com/llvm/llvm-project/commit/06c783567069db169ee2d1545a4bd3ffd0e3fec0.diff LOG: [lldb][test] Disable TestMultipleDebuggers again I did manage to turn a crash into a non-zero return code, but on the very first build it managed to time out. I thought I had the appetite to tweak timeouts but on second thought, I don't want yet another test to look out for. The test is not wrong, but on heavily loaded machines it's always going to be inherently unstable. Added: Modified: lldb/test/API/api/multiple-debuggers/TestMultipleDebuggers.py Removed: ################################################################################ diff --git a/lldb/test/API/api/multiple-debuggers/TestMultipleDebuggers.py b/lldb/test/API/api/multiple-debuggers/TestMultipleDebuggers.py index f0a3893f53aab..7d6fdd444791e 100644 --- a/lldb/test/API/api/multiple-debuggers/TestMultipleDebuggers.py +++ b/lldb/test/API/api/multiple-debuggers/TestMultipleDebuggers.py @@ -12,6 +12,10 @@ class TestMultipleSimultaneousDebuggers(TestBase): NO_DEBUG_INFO_TESTCASE = True + # Times out on heavily loaded Linux buildbots, don't want to get into tweaking + # the timeout per bot. Does work when run alone. See: + # https://github.com/llvm/llvm-project/issues/101162 + @skipIfLinux @skipIfNoSBHeaders @skipIfWindows @skipIfHostIncompatibleWithTarget _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
