[Lldb-commits] [PATCH] Add info on running remote test suite to the website

[Zachary Turner]

I know this is more work, but would it be possible to split all the testing
stuff out into a totally separate page on the sidebar?

On Tue, Apr 7, 2015 at 9:35 AM Pavel Labath <labath at google.com> wrote:

> Hi tberghammer, zturner,
>
> http://reviews.llvm.org/D8873
>
> Files:
>   www/build.html
>
> Index: www/build.html
> ===================================================================
> --- www/build.html
> +++ www/build.html
> @@ -402,6 +402,45 @@
>              <code>
>                <br />> python dotest.py -h
>              </code>
> +
> +            <p>
> +              Besides <code>dotest.py</code>, there is also
> <code>dosep.py</code>, which runs
> +              multiple instances of <code>dotest.py</code> in parallel,
> thereby greatly
> +              decreasing the time it takes to run the full testsuite. The
> number of concurrent
> +              tests is controlled by the <code>LLDB_TEST_THREADS</code>
> environment variable and
> +              defaults to the number of CPUs on your system. To pass
> additional options to
> +              <code>dotest.py</code>, specify those options as an
> <code>-o</code> argument to
> +              <code>dosep.py</code>. For example, the command
> +            </p>
> +            <code>python dosep.py -o "--executable bin/lldb -C
> bin/clang"</code>
> +            <p>
> +              will specify the lldb and clang executables to test for
> each dotest invocation.
> +              <code>ninja check-lldb</code> is wrapper around
> <code>dosep.py</code>.
> +            </p>
> +
> +            <h3>Running the test-suite remotely</h3>
> +
> +            <p>
> +              Running the test-suite remotely is supported both with
> <code>dotest.py</code> and
> +              <code>dosep.py</code>. The general process is the same as
> when running a local test
> +              suite, but there are two things to have in mind:
> +            </p>
> +            <ul>
> +              <li>
> +                You must have the <code>lldb-server</code> running on the
> remote system, ready to
> +                accept multiple connections. For more information on how
> to setup remote
> +                debugging see the <a href="remote.html">Remote
> debugging</a> page.
> +              </li>
> +              <li>
> +                You must tell the test-suite how to connect to the remote
> system. This is
> +                achieved using the <code>--platform-name</code>,
> <code>--platform-url</code> and
> +                <code>--platform-working-dir</code> parameters to
> <code>dotest.py</code>. These
> +                parameters correspond to the <code>platform select</code>
> and <code>platform
> +                connect</code> LLDB commands. You will usually also need
> to specify the compiler and
> +                architecture for the remote system.
> +              </li>
> +            </ul>
> +
>              <h2>Building API reference documentation</h2>
>              <p>
>                LLDB exposes a C++ as well as a Python API. To build the
> reference documentation for these two APIs, ensure you have
>
> EMAIL PREFERENCES
>   http://reviews.llvm.org/settings/panel/emailpreferences/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20150407/db8087b7/attachment.html>