[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://r
[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
show more ...
[lldb] Use assertState in more tests (NFC)Follow to D127355, converting more `assertEquals` to `assertState`.Differential Revision: https://reviews.llvm.org/D127378
Remove Python 2 checks from the test suiteWe dropped downstream support for Python 2 in the previous release. Nowthat we have branched for the next release the window where this kind ofchange cou
Remove Python 2 checks from the test suiteWe dropped downstream support for Python 2 in the previous release. Nowthat we have branched for the next release the window where this kind ofchange could introduce conflicts is closing too. Remove Python 2 checksfrom the test suite.Differential revision: https://reviews.llvm.org/D124429
[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
[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
[lldb] Remove support for replaying the test suite from a reproducerThis patch removes the infrastructure to replay the test suite from areproducer, as well as the modifications made to the indivi
[lldb] Remove support for replaying the test suite from a reproducerThis patch removes the infrastructure to replay the test suite from areproducer, as well as the modifications made to the individual tests.
[lldb] Use assertIn/NotIn over assertTrue/False (NFC)For improved failure messages, use `assertIn` over `assertTrue`.Differential Revision: https://reviews.llvm.org/D96095
[lldb] Skip TestStepScripted with reproducersSome of the test methods were already skipped because of an unexpectedpacket. The test started failing after it was expanded. Skip the wholetest with
[lldb] Skip TestStepScripted with reproducersSome of the test methods were already skipped because of an unexpectedpacket. The test started failing after it was expanded. Skip the wholetest with reproducers so we don't have to add the decorator for everymethod.
Add a setting to force stepping to always run all threads.Also allow ScriptedThreadPlans to set & get their StopOthersstate.<rdar://problem/64229484>Differential Revision: https://reviews.llvm.
Add a setting to force stepping to always run all threads.Also allow ScriptedThreadPlans to set & get their StopOthersstate.<rdar://problem/64229484>Differential Revision: https://reviews.llvm.org/D85265
[lldb/Reproducers] Differentiate active and passive replay unexpected packet.
[lldb/Test] Add skipIfReproducer for tests that diverge during replayAdd the skipIfReproducer decorator to the remaining tests that fail toreplay because the GDB remote packets diverge during repl
[lldb/Test] Add skipIfReproducer for tests that diverge during replayAdd the skipIfReproducer decorator to the remaining tests that fail toreplay because the GDB remote packets diverge during replay. This is*not* expected and should be fixed, but figuring out exactly what causedthe divergence has proven pretty difficult to track down.I've marked these tests as skipped for now so we can get clean resultsand detect new regressions. I have no evidence to believe that thesefailures have the same root cause, so I've not assigned them a PR.
[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/testcasesmkdi
[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