[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, test] Fix typos in the lldb testsReviewed By: JDevlieghereDifferential Revision: https://reviews.llvm.org/D126596
Fix the logic so stop-hooks get run after a breakpoint that ran an expressionCode was added to Target::RunStopHook to make sure that we don't run stop hooks whenyou stop after an expression evalua
Fix the logic so stop-hooks get run after a breakpoint that ran an expressionCode was added to Target::RunStopHook to make sure that we don't run stop hooks whenyou stop after an expression evaluation. But the way it was done was to check that wehadn't run an expression since the last natural stop. That failed in the case where youstopped for a breakpoint which had run an expression, because the stop-hooks get runafter the breakpoint actions, and so by the time we got to running the stop-hooks,we had already run a user expression.I fixed this by adding a target ivar tracking the last natural stop ID at which we hadrun a stop-hook. Then we keep track of this and make sure we run the stop-hooks onlyonce per natural stop.Differential Revision: https://reviews.llvm.org/D106514
Fix raciness in the StopHook check for "has the target run".This was looking at the privateState, but it's possible thatthe actual process has started up and then stopped again by thetime we get
Fix raciness in the StopHook check for "has the target run".This was looking at the privateState, but it's possible thatthe actual process has started up and then stopped again by thetime we get to the check, which would lead us to get out of runningthe stop hooks too early.Instead we need to track the intention of the stop hooks directly.Differential Revision: https://reviews.llvm.org/D88753
[lldb] Add missing import for LLDB test decorators to TestStopHookScriptedThis test wasn't using decorators before and was missing the import, so myprevious commit broke the test.
[lldb] Skip the flakey part of TestStopHookScripted on LinuxThis test seems to randomly fail on Linux machines. It's only one part of thetest failing randomly, so let's just skip it instead of rev
[lldb] Skip the flakey part of TestStopHookScripted on LinuxThis test seems to randomly fail on Linux machines. It's only one part of thetest failing randomly, so let's just skip it instead of reverting the wholepatch (again).
Revert "Revert "Add the ability to write target stop-hooks using the ScriptInterpreter.""This reverts commit f775fe59640a2e837ad059a8f40e26989d4f9831.I fixed a return type error in the original p
Revert "Revert "Add the ability to write target stop-hooks using the ScriptInterpreter.""This reverts commit f775fe59640a2e837ad059a8f40e26989d4f9831.I fixed a return type error in the original patch that was causing a test failure.Also added a REQUIRES: python to the shell test so we'll skip this forpeople who build lldb w/o Python.Also added another test for the error printing.
Revert "Add the ability to write target stop-hooks using the ScriptInterpreter."This temporarily reverts commit b65966cff65bfb66de59621347ffd97238d3f645while Jim figures out why the test is failin
Revert "Add the ability to write target stop-hooks using the ScriptInterpreter."This temporarily reverts commit b65966cff65bfb66de59621347ffd97238d3f645while Jim figures out why the test is failing on the bots.
Add the ability to write target stop-hooks using the ScriptInterpreter.Differential Revision: https://reviews.llvm.org/D88123
[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