Re: How might we mark a test suite isn't parallalizable?

On Thu, May 2, 2013 at 9:39 PM, brian d foy <[email protected]> wrote:
> In HARNESS_OPTIONS we can set -jN to note we want parallel tests
> running, but how can a particular module, which might be buried in the
> dependency chain, tell the harness it can't do that?
>
> It seems to me that by the time the tests are running, it's too late
> because they are already in parallel and the best we can do is issue a
> warning or decide to fail.

TAP::Harness already allows a module author to indicate which tests
can be run together and which not, using its rules feature. Not that
this feature is easily used from current build tools…

Leon