Lines Matching full:running

190 generic tests, so running the test suite with the feature enabled is a good way
199 feature. This can often be done by running the test suite with different
219     Launching a process and running to a breakpoint can often be the most
231     possible to test `SBValue` by running expressions with
234     Functionality that always requires a running process is everything that
238     environment also always require a running process.
256     ``@no_debug_info_test`` (which will avoid running all debug information
280     test executable and running the process to a breakpoint). Using these
301 When running the same command in LLDB the reason for the unexpected success
387 This tells the test harness that unless we are running "linux" and clang version equal & above 8.0,…
412 Running The Tests
418    debug interpreter, when running the test suite against a debug version of
426 Running the Full Test Suite
449 Running a Single Test Suite
452 Each test suite can be run separately, similar to running the whole test suite
465 Running a Single Test
493 Below is an overview of running individual test in the unit and API test suites
496 Running a Specific Test or Set of Tests: API Tests
499 In addition to running all the LLDB test suites with the ``check-lldb`` CMake
537 Running a Specific Test or Set of Tests: Unit Tests
556 Running the Test Suite Remotely
559 Running the test-suite remotely is similar to the process of running a local
562 1. You must have the lldb-server running on the remote system, ready to accept
572 Currently, running the remote test suite is supported only with ``dotest.py`` (or
576 Running tests in QEMU System Emulation Environment
618 …on35``, PTVS needs to know that this is the interpreter you want to use for running the test suite.