[Lldb-commits] [lldb] r240635 - Make XFAIL on TestPrintStackTraces more specific
Pavel Labath
labath at google.com
Thu Jun 25 05:16:50 PDT 2015
Author: labath
Date: Thu Jun 25 07:16:50 2015
New Revision: 240635
URL: http://llvm.org/viewvc/llvm-project?rev=240635&view=rev
Log:
Make XFAIL on TestPrintStackTraces more specific
the thread creation failure was fixed, but a backtracing problem remains in some situations.
Modified:
lldb/trunk/test/python_api/lldbutil/process/TestPrintStackTraces.py
Modified: lldb/trunk/test/python_api/lldbutil/process/TestPrintStackTraces.py
URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/test/python_api/lldbutil/process/TestPrintStackTraces.py?rev=240635&r1=240634&r2=240635&view=diff
==============================================================================
--- lldb/trunk/test/python_api/lldbutil/process/TestPrintStackTraces.py (original)
+++ lldb/trunk/test/python_api/lldbutil/process/TestPrintStackTraces.py Thu Jun 25 07:16:50 2015
@@ -18,10 +18,7 @@ class ThreadsStackTracesTestCase(TestBas
# 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."""
More information about the lldb-commits
mailing list