[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] Remove lldbtest.getBuildFlagsIt was being used only in some very old tests (which pass even withoutit) and its implementation is highly questionable.These days we have different mechanism
[lldb] Remove lldbtest.getBuildFlagsIt was being used only in some very old tests (which pass even withoutit) and its implementation is highly questionable.These days we have different mechanisms for requesting a build with aparticular kind of c++ library (USE_LIB(STD)CPP in the makefile).
[lldb] [test] Workaround symlink-related test failuresUse realpath() when spawning the executable create_after_attachto workaround a FreeBSD plugin (and possibly others) problem.If the executable
[lldb] [test] Workaround symlink-related test failuresUse realpath() when spawning the executable create_after_attachto workaround a FreeBSD plugin (and possibly others) problem.If the executable is started via a path containing a symlink, it isadded to the module list twice -- via the real and apparent path.This in turn cases the requested breakpoint to resolve twice.Use realpath() for main program path in lldb-vscode breakpoint teststo workaround a similar problem. If the passed path does not matchthe realpath, lldb-vscode does not report the breakpoints as verifiedand causes tests to fail.Since the underlying problems are non-trivial to fix and the purposeof these tests is not to reproduce symlink problems, let's applytrivial workarounds to make them pass.Differential Revision: https://reviews.llvm.org/D97230
[lldb] Convert more assertTrue to assertEqual (NFC)Follow up to D95813, this converts multiline assertTrue to assertEqual.Differential Revision: https://reviews.llvm.org/D95899
[lldb] [test] Link FreeBSD test failures to bugsDifferential Revision: https://reviews.llvm.org/D92740
[lldb] Enable FreeBSDRemote plugin by default and update test statusThe new FreeBSDRemote plugin has reached feature parity on i386and amd64 targets. Use it by default on these architectures, whi
[lldb] Enable FreeBSDRemote plugin by default and update test statusThe new FreeBSDRemote plugin has reached feature parity on i386and amd64 targets. Use it by default on these architectures, whileallowing the use of the legacy plugin via FREEBSD_LEGACY_PLUGIN envvar.Revisit the method of switching plugins. Apparently, the return valueof PlatformFreeBSD::CanDebugProcess() is what really decides whetherthe legacy or the new plugin is used.Update the test status. Reenable the tests that were previouslydisabled on FreeBSD and do not cause hangs or are irrelevant to FreeBSD.Mark all tests that fail reliably as expectedFailure. For now, teststhat are flaky (i.e. produce unstable results) are left enabledand cause unpredictable test failures.Differential Revision: https://reviews.llvm.org/D90757
[lldb/Test] Remove support for forking a subprocess from the test suite.Remove the forkSubprocess method and its bookkeeping.TestCreateAfterAttach is the only test using the fork method and I'm no
[lldb/Test] Remove support for forking a subprocess from the test suite.Remove the forkSubprocess method and its bookkeeping.TestCreateAfterAttach is the only test using the fork method and I'm notconvinced it adds enough to warrant the maintenance. Pavel suggested thesame thing in D83815.
[lldb/Test] Always set the cleanupSubprocesses tear down hookAlways clean up subprocesses on tear down instead of relying on thecaller to do so. This is not only less error prone but also means th
[lldb/Test] Always set the cleanupSubprocesses tear down hookAlways clean up subprocesses on tear down instead of relying on thecaller to do so. This is not only less error prone but also means thetests can be more concise.Differential revision: https://reviews.llvm.org/D83787
[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