Re: [PATCH 4/4] misc: document TESTSUITEFLAGS in README-hacking

[Akim Demaille]

Le 24 oct. 2012 à 14:12, Theophile Ranquet a écrit :

> +** TESTSUITEFLAGS
> +
> +The default is for make check to run all tests sequentially. This can be
> +very time consumming when checking repeatedly or on slower setups. This can
> +be sped up in two ways:
> +
> +Using -j[integer], in a make-like fashion, for example:

s/\[integer\]//

> +  $ make check TESTSUITEFLAGS='-j8'
> +
> +Running only the tests of a certain category, as specified in the AT files
> +with AT_KEYWORDS([[category]]). Currently supported categories are:

s/Currently supported //;s/are/include/.

> +  - c++, for c++ parsers
> +  - deprec, for tests concerning deprecated constructs.
> +  - glr, for glr parsers
> +  - java, for java parsers
> +  - report, for automaton dumps
> +
> +To run a specific set of tests, use -k (for "keyword"). For example:
> +  $ make check TESTSUITEFLAGS='-k c++'
> +
> +Both can be combined.
> +

Nice.

Please, fix the various issues, and push the updated series
of patches on gnu.org as the "next" branch.  You might need
to remove next first:

        git push origin :next
        git push origin HEAD:next