en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/commands/expression/top-level/TestTopLevelExprs.py#4cc8f2a0 [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 List of files: /llvm-project-15.0.7/lldb/test/API/commands/expression/top-level/TestTopLevelExprs.py Fri, 17 Jun 2022 00:38:47 +0000 Dave Lee <davelee.com@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/commands/expression/top-level/TestTopLevelExprs.py#69529286 Add a test for top-level expressions using "expr --top-level".This was broken for a while even though the Python versioncontinued to work. This adds a test so it doesn't regress. List of files: /llvm-project-15.0.7/lldb/test/API/commands/expression/top-level/TestTopLevelExprs.py Tue, 27 Jul 2021 20:36:21 +0000 Jim Ingham <jingham@apple.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/commands/expression/top-level/TestTopLevelExprs.py#71536fd0 [lldb] Fix that running a top level expression without a process fails with a cryptic errorRight now when running `expr --top-level -- void foo() {}`, LLDB just prints a cryptic`error: Couldn't find $__lldb_expr() in the module` error. The reason for that isthat if we don't have a running process, we try to set our execution policy to always use theIR interpreter (ExecutionPolicyNever) which works even without a process. Howeverthat code didn't consider the special ExecutionPolicyTopLevel which we use fortop-level expressions. By changing the execution policy to ExecutionPolicyNever,LLDB thinks we're actually trying to interpret a normal expression inside our`$__lldb_expr` function and then fails when looking for it.This just adds an exception for top-level expressions to that code and a bunch of tests.Reviewed By: shafikDifferential Revision: https://reviews.llvm.org/D91723 List of files: /llvm-project-15.0.7/lldb/test/API/commands/expression/top-level/TestTopLevelExprs.py Thu, 11 Feb 2021 16:00:17 +0000 Raphael Isemann <teemperor@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/commands/expression/top-level/TestTopLevelExprs.py#99451b44 [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 List of files: /llvm-project-15.0.7/lldb/test/API/commands/expression/top-level/TestTopLevelExprs.py Tue, 11 Feb 2020 18:01:16 +0000 Jordan Rupprecht <rupprecht@google.com>