From 9d59306528f84c72c5a3d11145c404296979b552 Mon Sep 17 00:00:00 2001 From: Zachary Turner Date: Tue, 12 Jan 2016 20:45:29 +0000 Subject: Fix TestThreadJump on Windows. The system can create threads for a system threadpool, so there is no guarantee that the thread that is stopped is thread 1. So use a more robust check. llvm-svn: 257513 --- .../lldbsuite/test/functionalities/thread/jump/TestThreadJump.py | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'lldb/packages/Python') diff --git a/lldb/packages/Python/lldbsuite/test/functionalities/thread/jump/TestThreadJump.py b/lldb/packages/Python/lldbsuite/test/functionalities/thread/jump/TestThreadJump.py index be49a210f0f..9240311aa3a 100644 --- a/lldb/packages/Python/lldbsuite/test/functionalities/thread/jump/TestThreadJump.py +++ b/lldb/packages/Python/lldbsuite/test/functionalities/thread/jump/TestThreadJump.py @@ -34,8 +34,7 @@ class ThreadJumpTestCase(TestBase): # The stop reason of the thread should be breakpoint 1. self.expect("thread list", STOPPED_DUE_TO_BREAKPOINT + " 1", substrs = ['stopped', - '* thread #1', - 'stop reason = breakpoint 1']) + 'main.cpp:{}, stop reason = breakpoint 1'.format(self.mark3)]) self.do_min_test(self.mark3, self.mark1, "i", "4"); # Try the int path, force it to return 'a' self.do_min_test(self.mark3, self.mark2, "i", "5"); # Try the int path, force it to return 'b' -- cgit v1.2.3