From 35a24ded0ae76ce3c2575b69a26461598465d74f Mon Sep 17 00:00:00 2001 From: Pavel Labath Date: Thu, 25 Jun 2015 12:16:50 +0000 Subject: [PATCH] Make XFAIL on TestPrintStackTraces more specific the thread creation failure was fixed, but a backtracing problem remains in some situations. llvm-svn: 240635 --- .../test/python_api/lldbutil/process/TestPrintStackTraces.py | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/lldb/test/python_api/lldbutil/process/TestPrintStackTraces.py b/lldb/test/python_api/lldbutil/process/TestPrintStackTraces.py index f8a94ee04546..d70417c937a8 100644 --- a/lldb/test/python_api/lldbutil/process/TestPrintStackTraces.py +++ b/lldb/test/python_api/lldbutil/process/TestPrintStackTraces.py @@ -18,10 +18,7 @@ class ThreadsStackTracesTestCase(TestBase): # Find the line number to break inside main(). self.line = line_number('main.cpp', '// Set break point at this line.') - # fails on Linux i386 llvm.org/pr23043 - # fails 78/100 on Linux x86_64 when running against remote lldb-platform - # failed 11/200 on the linux build bot - @expectedFailureLinux + @expectedFailureAll("llvm.org/pr23043", ["linux"], "gcc", archs=["i386"]) # We are unable to produce a backtrace of the main thread when the thread is blocked in fgets @python_api_test def test_stack_traces(self): """Test SBprocess and SBThread APIs with printing of the stack traces."""