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
On Thu, May 02, 2013 at 02:39:13PM -0500, brian d foy 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?
When can a test not be parallelizable? Mos
On 05/02/2013 03:39 PM, brian d foy 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, i
> When can a test not be parallelizable? Most of the examples that I can
> think of (depending on a file resource, etc) smell like a design failure.
> Tests should usually be able to use a unique temp file, etc.
Here's an example:
Say you are testing a web application that does a bulk export of
In accordance with the terms of my grant from TPF this is the monthly
report for my work on improving Devel::Cover covering April 2013.
April has been a very busy time for me outside of grant work on Devel::Cover.
Apart from other matters, I was fortunate enough to be able to attend the Perl
QA Ha
In accordance with the terms of my grant from TPF this is the monthly
report for my work on improving Devel::Cover covering March 2013.
Sorry for the delay in this report. Most of March and all of April has been a
very busy time for me outside of grant work on Devel::Cover.
This month I released
