[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] Use assertIn/NotIn over assertTrue/False (NFC)For improved failure messages, use `assertIn` over `assertTrue`.Differential Revision: https://reviews.llvm.org/D96095
[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
Harmonize Python shebangDifferential Revision: https://reviews.llvm.org/D83857
[lldb/Properties] Move OSPluginReportsAllThreads from Target to ProcessThis is what Jim wanted originally.rdar://problem/61236293Differential revision: https://reviews.llvm.org/D80159
Disable two new tests on Windows. They are failing but the logs are not helpful.Also turn on the command trace unconditionally for TestThreadPlanCommands.py as thetests for the Ubuntu bot don't s
Disable two new tests on Windows. They are failing but the logs are not helpful.Also turn on the command trace unconditionally for TestThreadPlanCommands.py as thetests for the Ubuntu bot don't seem to run with -t making it hard to see why this isfailing remotely.
Allow the ThreadPlanStackMap to hold the thread plans for threadsthat were not reported by the OS plugin. To facilitate this, moveadding/updating the ThreadPlans for a Thread to the ThreadPlanStac
Allow the ThreadPlanStackMap to hold the thread plans for threadsthat were not reported by the OS plugin. To facilitate this, moveadding/updating the ThreadPlans for a Thread to the ThreadPlanStackMap.Also move dumping thread plans there as well.Added some tests for "thread plan list" and "thread plan discard" sinceI didn't seem to have written any originally.Differential Revision: https://reviews.llvm.org/D76814