[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] Skip tests failing with GCC due to LLDB not being able to call constructorsTracked in llvm.org/pr50814These tests fail with all GCC versions I tested (8.5, 9.4, 10.3, 11.1).
[lldb/test] Catch invalid calls to expect()Add preconditions to `TestBase.expect()` that catch semantically invalid callsthat happen to succeed anyway. This also fixes the broken callsites caught
[lldb/test] Catch invalid calls to expect()Add preconditions to `TestBase.expect()` that catch semantically invalid callsthat happen to succeed anyway. This also fixes the broken callsites caught bythese checks.This prevents the following incorrect calls:1. `self.expect("lldb command", "some substr")`2. `self.expect("lldb command", "assert message", "some substr")`Differential Revision: https://reviews.llvm.org/D88792
[lldb] Skip failing parts of TestCppConstructors that use 'new' on Windows
[lldb] Let TestCppConstructors pass without fix-it interventionThis should use -> instead of '.', but the fix-it functionality ofthe expression evaluator saved us here. Let's use the proper syntax
[lldb] Let TestCppConstructors pass without fix-it interventionThis should use -> instead of '.', but the fix-it functionality ofthe expression evaluator saved us here. Let's use the proper syntaxin the first place as we don't want to test fix-its here.
[lldb][NFC] Add a missing test case to TestCppConstructors.py
[lldb] Make TestFormatters.py not rely on working constructor callsAll calls to operator new in this test fail for me with:```expression --show-types -- *(new foo(47))`Error output:error: Execu
[lldb] Make TestFormatters.py not rely on working constructor callsAll calls to operator new in this test fail for me with:```expression --show-types -- *(new foo(47))`Error output:error: Execution was interrupted, reason: internal c++ exception breakpoint(-6)..The process has been returned to the state before expression evaluation.```As calling operator new isn't the idea of this test, this patch moves thatlogic to the binary with some new_* utility functions and explicitly teststhis logic in the constructor test (where we can isolate the failures andskip them on Linux).
[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