From 1d9284c3bc985f4fc9415aae5981332b395354e4 Mon Sep 17 00:00:00 2001 From: Jim Ingham Date: Thu, 20 Oct 2016 22:49:06 +0000 Subject: [PATCH] Remove an unnecessary and incorrect check for num locations of a breakpoint by grubbing the break list output. If you pass a number of locations into the run_break_* functions, they will check that this is right for you. llvm-svn: 284791 --- .../functionalities/thread/multi_break/TestMultipleBreakpoints.py | 8 -------- 1 file changed, 8 deletions(-) diff --git a/lldb/packages/Python/lldbsuite/test/functionalities/thread/multi_break/TestMultipleBreakpoints.py b/lldb/packages/Python/lldbsuite/test/functionalities/thread/multi_break/TestMultipleBreakpoints.py index 01988dd..18d88cb 100644 --- a/lldb/packages/Python/lldbsuite/test/functionalities/thread/multi_break/TestMultipleBreakpoints.py +++ b/lldb/packages/Python/lldbsuite/test/functionalities/thread/multi_break/TestMultipleBreakpoints.py @@ -45,14 +45,6 @@ class MultipleBreakpointTestCase(TestBase): lldbutil.run_break_set_by_file_and_line( self, "main.cpp", self.breakpoint, num_expected_locations=1) - # The breakpoint list should show 1 location. - self.expect( - "breakpoint list -f", - "Breakpoint location shown correctly", - substrs=[ - "1: file = 'main.cpp', line = %d, locations = 1" % - self.breakpoint]) - # Run the program. self.runCmd("run", RUN_SUCCEEDED) -- 2.7.4