forked from OSchip/llvm-project
[lldbsuite] Mark the TestScriptedResolver tests as XFAIL on Windows
Summary: They fail similarly to some of the other breakpoint tests on Windows, so I suspect the cause is the same. I've linked to the same bug. Reviewers: asmith, zturner, jingham Subscribers: abidh, lldb-commits Differential Revision: https://reviews.llvm.org/D53331 llvm-svn: 344744
This commit is contained in:
parent
b0b5312e67
commit
c3439b0995
|
@ -10,6 +10,7 @@ import time
|
||||||
import re
|
import re
|
||||||
import lldb
|
import lldb
|
||||||
import lldbsuite.test.lldbutil as lldbutil
|
import lldbsuite.test.lldbutil as lldbutil
|
||||||
|
from lldbsuite.test.decorators import *
|
||||||
from lldbsuite.test.lldbtest import *
|
from lldbsuite.test.lldbtest import *
|
||||||
|
|
||||||
|
|
||||||
|
@ -19,17 +20,20 @@ class TestScriptedResolver(TestBase):
|
||||||
|
|
||||||
NO_DEBUG_INFO_TESTCASE = True
|
NO_DEBUG_INFO_TESTCASE = True
|
||||||
|
|
||||||
|
@expectedFailureAll(oslist=["windows"], bugnumber="llvm.org/pr24528")
|
||||||
def test_scripted_resolver(self):
|
def test_scripted_resolver(self):
|
||||||
"""Use a scripted resolver to set a by symbol name breakpoint"""
|
"""Use a scripted resolver to set a by symbol name breakpoint"""
|
||||||
self.build()
|
self.build()
|
||||||
self.do_test()
|
self.do_test()
|
||||||
|
|
||||||
|
@expectedFailureAll(oslist=["windows"], bugnumber="llvm.org/pr24528")
|
||||||
def test_search_depths(self):
|
def test_search_depths(self):
|
||||||
""" Make sure we are called at the right depths depending on what we return
|
""" Make sure we are called at the right depths depending on what we return
|
||||||
from __get_depth__"""
|
from __get_depth__"""
|
||||||
self.build()
|
self.build()
|
||||||
self.do_test_depths()
|
self.do_test_depths()
|
||||||
|
|
||||||
|
@expectedFailureAll(oslist=["windows"], bugnumber="llvm.org/pr24528")
|
||||||
def test_command_line(self):
|
def test_command_line(self):
|
||||||
""" Make sure we are called at the right depths depending on what we return
|
""" Make sure we are called at the right depths depending on what we return
|
||||||
from __get_depth__"""
|
from __get_depth__"""
|
||||||
|
|
Loading…
Reference in New Issue