Changes in TestMultipleHits.py

2238dcc39358353cac21df75c3c3286ab20b8f53 - [NFC][Py Reformat] Reformat python files in lldb

Thu, 25 May 2023 15:48:57 +0000

[NFC][Py Reformat] Reformat python files in lldbThis is an ongoing series of commits that are reformatting our Pythoncode. Reformatting is done with `black` (23.1.0).If you end up having problems merging this commit because you have madechanges to a python file, the best way to handle that is to run `gitcheckout --ours ` and then reformat it with black.RFC: https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-styleDifferential revision: https://reviews.llvm.org/D151460 List of files: /llvm-project/lldb/test/API/commands/watchpoints/multiple_hits/TestMultipleHits.py

0f821339dad1bf45dd71a1cac32b6352ba251ecb - [lldb] Add assertStopReason helper function

Wed, 03 Aug 2022 18:42:12 +0000

[lldb] Add assertStopReason helper functionAdd a function to make it easier to debug a test failure caused by anunexpected stop reason. This is similar to the assertState helper thatwas added in ce825e46743b.Before: self.assertEqual(stop_reason, lldb.eStopReasonInstrumentation) AssertionError: 5 != 10After: self.assertStopReason(stop_reason, lldb.eStopReasonInstrumentation) AssertionError: signal (5) != instrumentation (10)Differential revision: https://reviews.llvm.org/D131083 List of files: /llvm-project/lldb/test/API/commands/watchpoints/multiple_hits/TestMultipleHits.py

4cc8f2a017c76af25234afc7c380550e9c93135c - [lldb][tests] Automatically call compute_mydir (NFC)

Fri, 17 Jun 2022 00:38:47 +0000

[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/lldb/test/API/commands/watchpoints/multiple_hits/TestMultipleHits.py

47c4c6a7469f3fd3e364a9b3669838686d4f1de6 - [lldb] Use assertState in more tests (NFC)

Thu, 09 Jun 2022 05:22:27 +0000

[lldb] Use assertState in more tests (NFC)Follow to D127355, converting more `assertEquals` to `assertState`.Differential Revision: https://reviews.llvm.org/D127378 List of files: /llvm-project/lldb/test/API/commands/watchpoints/multiple_hits/TestMultipleHits.py

779bbbf27fe631154bdfaac7a443f198d4654688 - [lldb] Replace asserts on .Success() with assertSuccess()

Sat, 12 Feb 2022 05:23:16 +0000

[lldb] Replace asserts on .Success() with assertSuccess()Replace forms of `assertTrue(err.Success())` with `assertSuccess(err)` (added in D82759).* `assertSuccess` prints out the error's message* `assertSuccess` expresses explicit higher level semantics, both to the reader and for test failure output* `assertSuccess` seems not to be well known, using it where possible will help spread knowledge* `assertSuccess` statements are more succinctDifferential Revision: https://reviews.llvm.org/D119616 List of files: /llvm-project/lldb/test/API/commands/watchpoints/multiple_hits/TestMultipleHits.py

54c2687292da54a2d7964a47b0e334155385f084 - [lldb] Introduce createTestTarget for creating a valid target in API tests

Mon, 24 May 2021 14:01:48 +0000

[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/lldb/test/API/commands/watchpoints/multiple_hits/TestMultipleHits.py

99451b4453688a94c6014cac233d371ab4cc342d - [lldb][test] Remove symlink for API tests.

Tue, 11 Feb 2020 18:01:16 +0000

[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/lldb/test/API/commands/watchpoints/multiple_hits/TestMultipleHits.py