[Lldb-commits] [lldb] 0e0e381 - This test seems to pass on Linux, remove the x-fail.

[Jim Ingham via lldb-commits]

Author: Jim Ingham
Date: 2022-02-14T16:58:57-08:00
New Revision: 0e0e381a1547c641a54b2131665d8a38855371b4

URL: https://github.com/llvm/llvm-project/commit/0e0e381a1547c641a54b2131665d8a38855371b4
DIFF: https://github.com/llvm/llvm-project/commit/0e0e381a1547c641a54b2131665d8a38855371b4.diff

LOG: This test seems to pass on Linux, remove the x-fail.

One of the tests in this test setup was copied from a more complex test, and I didn't know
if the setup or the subsequent parts of the test were the ones that fail on Linux.  Looks
like it was the latter, so let's mark this succeeding.

Added: 
    

Modified: 
    lldb/test/API/commands/thread/backtrace/TestThreadBacktraceRepeat.py

Removed: 
    


################################################################################
diff  --git a/lldb/test/API/commands/thread/backtrace/TestThreadBacktraceRepeat.py b/lldb/test/API/commands/thread/backtrace/TestThreadBacktraceRepeat.py
index 5a737bc174337..998ade04985ab 100644
--- a/lldb/test/API/commands/thread/backtrace/TestThreadBacktraceRepeat.py
+++ b/lldb/test/API/commands/thread/backtrace/TestThreadBacktraceRepeat.py
@@ -95,9 +95,6 @@ def check_two_threads(self, result_str, thread_id_1, name_1, thread_id_2, name_2
     # the comments whether it was getting two threads to the same breakpoint that was
     # problematic, or the step-out part.  This test stops at the rendevous point so I'm
     # removing the skipIfLinux to see if we see any flakiness in just this part of the test.
-    @expectedFailureAll(
-        oslist=["linux"],
-        bugnumber="llvm.org/pr23477 Test occasionally times out on the Linux build bot")
     @expectedFailureAll(
         oslist=["freebsd"],
         bugnumber="llvm.org/pr18066 inferior does not exit")