en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/functionalities/breakpoint/breakpoint_ignore_count/TestBreakpointIgnoreCount.py#4cc8f2a0 [lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://reviews.llvm.org/D128077 List of files: /llvm-project-15.0.7/lldb/test/API/functionalities/breakpoint/breakpoint_ignore_count/TestBreakpointIgnoreCount.py Fri, 17 Jun 2022 00:38:47 +0000 Dave Lee <davelee.com@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/functionalities/breakpoint/breakpoint_ignore_count/TestBreakpointIgnoreCount.py#9f0b5f9a [lldb/test] Added lldbutil function to test a breakpointTesting the breakpoint itself rather than the lldb string.Differential Revision: https://reviews.llvm.org/D111899 List of files: /llvm-project-15.0.7/lldb/test/API/functionalities/breakpoint/breakpoint_ignore_count/TestBreakpointIgnoreCount.py Wed, 17 Nov 2021 08:37:30 +0000 SYNOPSYS\georgiev <georgiev@synopsys.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/functionalities/breakpoint/breakpoint_ignore_count/TestBreakpointIgnoreCount.py#658f6ed1 Make ignore counts work as "after stop" modifiers so they play nicely with conditionsPreviously ignore counts were checked when we stopped to do the sync callback in Breakpoint::ShouldStop. That meant we would do all the ignore count work even whenthere is also a condition says the breakpoint should not stop.That's wrong, lldb treats breakpoint hits that fail the thread or condition checks as "not having hit the breakpoint". So the ignore count check should happen afterthe condition and thread checks in StopInfoBreakpoint::PerformAction.The one side-effect of doing this is that if you have a breakpoint with a synchronous callback, it will run the synchronous callback before checking the ignore count.That is probably a good thing, since this was already true of the condition and thread checks, so this removes an odd asymmetry. And breakpoints with sync callbacksare all internal lldb breakpoints and there's not a really good reason why you would want one of these to use an ignore count (but not a condition or thread check...)Differential Revision https://reviews.llvm.org/D103217 List of files: /llvm-project-15.0.7/lldb/test/API/functionalities/breakpoint/breakpoint_ignore_count/TestBreakpointIgnoreCount.py Tue, 01 Jun 2021 23:14:08 +0000 Jim Ingham <jingham@apple.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/functionalities/breakpoint/breakpoint_ignore_count/TestBreakpointIgnoreCount.py#54c26872 [lldb] Introduce createTestTarget for creating a valid target in API testsAt the moment nearly every test calls something similar to`self.dbg.CreateTarget(self.getBuildArtifact("a.out"))` and them sometimeschecks if the created target is actually valid with something like`self.assertTrue(target.IsValid(), "some useless text")`.Beside being really verbose the error messages generated by this pattern arealways just indicating that the target failed to be created but now why.This patch introduces a helper function `createTestTarget` to our Test classthat creates the target with the much more verbose `CreateTarget` overload thatgives us back an SBError (with a fancy error). If the target couldn't be createdthe function prints out the SBError that LLDB returned and asserts for us. Italso defaults to the "a.out" build artifact path that nearly all tests are usingto avoid to hardcode "a.out" in every test.I converted a bunch of tests to the new function but I'll do the rest of thetest suite as follow ups.Reviewed By: JDevlieghereDifferential Revision: https://reviews.llvm.org/D102771 List of files: /llvm-project-15.0.7/lldb/test/API/functionalities/breakpoint/breakpoint_ignore_count/TestBreakpointIgnoreCount.py Mon, 24 May 2021 14:01:48 +0000 Raphael Isemann <teemperor@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/functionalities/breakpoint/breakpoint_ignore_count/TestBreakpointIgnoreCount.py#619e2e09 [lldb] Convert assertTrue(a == b) to assertEqual(a, b)Convert `assertTrue(a == b)` to `assertEqual(a, b)` to produce better failure messages.These were mostly done via regex search & replace, with some manual fixes.Differential Revision: https://reviews.llvm.org/D95813 List of files: /llvm-project-15.0.7/lldb/test/API/functionalities/breakpoint/breakpoint_ignore_count/TestBreakpointIgnoreCount.py Mon, 01 Feb 2021 20:01:32 +0000 Dave Lee <davelee.com@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/functionalities/breakpoint/breakpoint_ignore_count/TestBreakpointIgnoreCount.py#99451b44 [lldb][test] Remove symlink for API tests.Summary: Moves lldbsuite tests to lldb/test/API.This is a largely mechanical change, moved with the following steps:```rm lldb/test/API/testcasesmkdir -p lldb/test/API/{test_runner/test,tools/lldb-{server,vscode}}mv lldb/packages/Python/lldbsuite/test/test_runner/test lldb/test/API/test_runnerfor d in $(find lldb/packages/Python/lldbsuite/test/* -maxdepth 0 -type d | egrep -v "make|plugins|test_runner|tools"); do mv $d lldb/test/API; donefor d in $(find lldb/packages/Python/lldbsuite/test/tools/lldb-vscode -maxdepth 1 -mindepth 1 | grep -v ".py"); do mv $d lldb/test/API/tools/lldb-vscode; donefor d in $(find lldb/packages/Python/lldbsuite/test/tools/lldb-server -maxdepth 1 -mindepth 1 | egrep -v "gdbremote_testcase.py|lldbgdbserverutils.py|socket_packet_pump.py"); do mv $d lldb/test/API/tools/lldb-server; done```lldb/packages/Python/lldbsuite/__init__.py and lldb/test/API/lit.cfg.py were also updated with the new directory structure.Reviewers: labath, JDevlieghereTags: #lldbDifferential Revision: https://reviews.llvm.org/D71151 List of files: /llvm-project-15.0.7/lldb/test/API/functionalities/breakpoint/breakpoint_ignore_count/TestBreakpointIgnoreCount.py Tue, 11 Feb 2020 18:01:16 +0000 Jordan Rupprecht <rupprecht@google.com>