# from Eden Cardim
# on Monday 18 July 2011 11:53:
>> Moving out of the realm of what you can do today, it may be
>> worth adding a key to the meta file which indicates the
>> tests are not safe for parallel testing.
>
>I'm not sure I see how to accomplish that, given the meta file is
> under the
> "Michael" == Michael G Schwern writes:
Michael> Just to make sure, when you say "using several cores" you mean
testing in
Michael> parallel? Like setting the jobs flag (or -j with prove)?
Yes exactly.
Michael> I don't like work arounds for test failures, and what
Michael>
On Sun, Jul 17, 2011 at 11:47:52AM -0700, Michael G Schwern wrote:
> Moving out of the realm of what you can do today, it may be worth adding a key
> to the meta file which indicates the tests are not safe for parallel testing.
>
> I prefer this over the inverse (a flag stating that the tests ARE
On 2011.7.14 6:00 PM, Eden Cardim wrote:
> It appears there are several distributions on CPAN whose tests don't
> pass when using several cores. This is an annoyance because some of the
> larger deplists nearly always have a module with broken tests in them,
> so testing can't just be a fire-and-fo
Hello Everyone,
It appears there are several distributions on CPAN whose tests don't
pass when using several cores. This is an annoyance because some of the
larger deplists nearly always have a module with broken tests in them,
so testing can't just be a fire-and-forget operation, it also confuse
On Thu, Oct 16, 2003 at 11:12:53AM -0700, chromatic wrote:
> On Thu, 2003-10-16 at 10:46, Ovid wrote:
>
> > I was browsing through the Perl core tests and I saw that some tests in the t/uni/
> > directory used
> > Test::More, but most other tests would explicitly '
Chromatic wrote in perl.qa :
>
> Stuff in t/op mostly can't use Test or Test::More because those modules
> rely on the features being tested. Most everything else can use
> Test::More. Barring any Unicode-related fiascos (of which I am proudly
> and blissfully unaware), they probably haven't bee
On Thu, 2003-10-16 at 10:46, Ovid wrote:
> I was browsing through the Perl core tests and I saw that some tests in the t/uni/
> directory used
> Test::More, but most other tests would explicitly 'print "ok 1\n"'.
>
> Is this to reduce the dependancy of the cor
I was browsing through the Perl core tests and I saw that some tests in the t/uni/
directory used
Test::More, but most other tests would explicitly 'print "ok 1\n"'.
Is this to reduce the dependancy of the core tests on external modules (and if so, why
does t/uni/
not follo
On Sat, Aug 25, 2001 at 02:56:30PM +0100, Tony Bowden wrote:
> > Everything in lib/. For t/ you'll have to use your judgement. I
> > added some stuff about this into perlhack.pod in bleadperl (attached).
>
> I'm not sure I have enough judgement for this yet! :)
>
> I'm currently adding stuff t
On Mon, Aug 20, 2001 at 05:30:26PM -0400, Michael G Schwern wrote:
> On Mon, Aug 20, 2001 at 02:16:37AM +0100, Tony Bowden wrote:
> > In rewriting core tests with Test::More, where can we start?
>
> Everything in lib/. For t/ you'll have to use your judgement. I
> adde
In rewriting core tests with Test::More, where can we start?
i.e. if the earlier tests are building up functionality bit by bit,
so you can't rely on anything too complex, at what ponit in the test
suite does it become acceptable to bring in the heavy guns of Test::More?
12 matches
Mail list logo
