[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] Convert more assertTrue to assertEqual (NFC)Follow up to D95813, this converts multiline assertTrue to assertEqual.Differential Revision: https://reviews.llvm.org/D95899
[lldb] Don't ask for QOS_CLASS_UNSPECIFIED queue in TestQueuesTestQueues is curiously failing for me as my queue for QOS_CLASS_UNSPECIFIEDis named "Utility" and not "User Initiated" or "Default".
[lldb] Don't ask for QOS_CLASS_UNSPECIFIED queue in TestQueuesTestQueues is curiously failing for me as my queue for QOS_CLASS_UNSPECIFIEDis named "Utility" and not "User Initiated" or "Default". While debugging, thisI noticed that this test isn't actually using this API right from what I understand. The API documentationfor `dispatch_get_global_queue` specifies for the parameter: "You may specify the valueQOS_CLASS_USER_INTERACTIVE, QOS_CLASS_USER_INITIATED, QOS_CLASS_UTILITY, or QOS_CLASS_BACKGROUND."QOS_CLASS_UNSPECIFIED isn't listed as one of the supported values. swift-corelibs-libdispatcheven checks for this value and returns a DISPATCH_BAD_INPUT. Thelibdispatch shipped on macOS seems to also check for QOS_CLASS_UNSPECIFIED and seems toinstead cause a "client crash", but somehow this doesn't trigger in this test and instead we justget whatever queueThis patch just removes that part of the test as it appears the code is just incorrect.Reviewed By: jasonmolendaDifferential Revision: https://reviews.llvm.org/D86211
[lldb] Make error messages in TestQueues more helpfull
[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