From 2c5f0c1b7f869ad9f9378520daa12da12be012f7 Mon Sep 17 00:00:00 2001 From: Matthias Maier Date: Tue, 7 Apr 2015 11:34:25 +0200 Subject: [PATCH] Testsuite: Update documentation, remove obsolete paragraph --- doc/developers/testsuite.html | 24 ------------------------ 1 file changed, 24 deletions(-) diff --git a/doc/developers/testsuite.html b/doc/developers/testsuite.html index 5d293d4aa6..327cb3702d 100644 --- a/doc/developers/testsuite.html +++ b/doc/developers/testsuite.html @@ -43,7 +43,6 @@
  • Running the testsuite
    1. How to interpret the output
    2. -
    3. Parallelizing testsuite configuration
    4. Generating coverage information
  • Testsuite development
  • @@ -295,29 +294,6 @@ xx: =============================== OUTPUT END ============================

    - -

    Parallelizing testsuite configuration

    - -

    - If you have set up the testsuite (or at least a few hundred tests by - providing a sufficiently general regular expression - as TEST_PICKUP_REGEX) you'll notice that a - reconfiguration of the build directory takes a noticeable time (in the - order of minutes instead of seconds) with - Reconfiguring testsuite subprojects. - By default (with the "Unix Makefiles" generator) this is due to the - fact that the reconfiguration processes the subprojects sequentally. - If you want to increase the parallelism, specify e.g. - MAKEOPTS="-j8" as environment variable or as CMake - variable. -

    -

    - Alternatively, you can use Ninja as your build tool instead - of make. -

    - - -

    Generating coverage information

    -- 2.39.5