[lldb] Use assertState in even more tests (NFC)Followup to D127355 and D127378, converting more instances ofassertEqual to assertState.
[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] 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] Replace unittest2.expectedFailure with expectedFailure (NFC)Rename the existing expectedFailure to expectedFailureIfFn to betterdescribe its purpose and provide an overload forunittest2.ex
[lldb] Replace unittest2.expectedFailure with expectedFailure (NFC)Rename the existing expectedFailure to expectedFailureIfFn to betterdescribe its purpose and provide an overload forunittest2.expectedFailure in decorators.py.
[lldb] Remove license headers from all test source filesSummary:Around a third of our test sources have LLVM license headers. This patch removes those headers from all testsources and also fixes
[lldb] Remove license headers from all test source filesSummary:Around a third of our test sources have LLVM license headers. This patch removes those headers from all testsources and also fixes any tests that depended on the length of the license header.The reasons for this are:* A few tests verify line numbers and will start failing if the number of lines in the LLVM license header changes. Once I landed my patch for valid SourceLocations in debug info we will probably have even more tests that verify line numbers.* No other LLVM project is putting license headers in its test files to my knowledge.* They make the test sources much more verbose than they have to be. Several tests have longer license headers than the actual test source.For the record, the following tests had their line numbers changed to pass with the removal of the license header: lldb-api :: functionalities/breakpoint/breakpoint_by_line_and_column/TestBreakpointByLineAndColumn.py lldb-shell :: Reproducer/TestGDBRemoteRepro.test lldb-shell :: Reproducer/TestMultipleTargets.test lldb-shell :: Reproducer/TestReuseDirectory.test lldb-shell :: ExecControl/StopHook/stop-hook-threads.test lldb-shell :: ExecControl/StopHook/stop-hook.test lldb-api :: lang/objc/exceptions/TestObjCExceptions.pyReviewers: #lldb, espindola, JDevlieghereReviewed By: #lldb, JDevlieghereSubscribers: emaste, aprantl, arphaman, JDevlieghere, lldb-commitsTags: #lldbDifferential Revision: https://reviews.llvm.org/D74839
[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