Hi!
On Sat, Sep 23, 2006 at 03:30:06PM -0600, Randy J. Ray wrote:
I asked this once before, but rather than getting an answer, someone just
did it. There are some modules that I've deleted completely from CPAN; one
was because I renamed the top-level of the namespace (per conversation with
Hi all,
I have troubles building Test-Simple-0.64 on a standard SL3 machine:
perl Makefile.PL
make
make test
several threading related tests fail, e.g.:
-
t/threads.Thread 1 terminated abnormally: lock can only be
used on shared values at
On Monday 25 September 2006 02:41, Florian Scharinger wrote:
I have troubles building Test-Simple-0.64 on a standard SL3 machine:
perl Makefile.PL
make
make test
several threading related tests fail, e.g.:
-
t/threads.Thread 1 terminated abnormally: lock
From: Florian Scharinger
I have troubles building Test-Simple-0.64 on a standard SL3 machine:
snip
several threading related tests fail, e.g.:
snip
-bash-2.05b$ perl -V
Summary of my perl5 (revision 5.0 version 8 subversion 0) configuration:
From the Test::Simple Changes file for
Thx for the quick replies (also to Ovid). I'll see if we can upgrade to
= 5.8.1, let's see.
Florian.
On Mon, 25 Sep 2006, chromatic wrote:
On Monday 25 September 2006 02:41, Florian Scharinger wrote:
I have troubles building Test-Simple-0.64 on a standard SL3 machine:
perl
On 9/25/06, Gabor Szabo [EMAIL PROTECTED] wrote:
I think the above (and maybe the rest of the details) should be included
in the success reports as well.
Sometimes there seem to be two reports from the same source a failure
and then a success. It would be very useful to be able to see what has
Chris Dolan wrote:
On Sep 24, 2006, at 5:42 PM, Christopher H. Laco wrote:
Ok, I'll play your game. :-)
http://perlcritic.tigris.org/svn/perlcritic/trunk/Perl-Critic/lib/Perl/Critic/Policy/Testing/
[Assuming I'm not silly] Empty! Rev. 667
-=Chris
D'oh! SVN commits work better if
While trying to install the latest PPI from svn, I noticed that running
'dmake test' passed, and 'prove -b t/' failed.
As more and more people use Module::Install, it seems more and more
transient build/test related modules are being stuffed in the inc/
directory.
Given the talk about installers
Two tickets on CPAN::Reporter have prompted the question of the role
of CPAN Testers in capturing build failures versus test failures --
i.e. failures in Makefile.PL/Build.PL or in make/Build.
* http://rt.cpan.org/Public/Bug/Display.html?id=21691
*
BTW, my Directory::Scratch module is meant to solve this problem. At
the top of your program you:
use Directory::Scratch YourOS
and all path names passed to the module are interpreted as though
they're from YourOS, even when running on some other OS. This means
that you can use UNIX path
Smolder 1.00 has finally been tagged and released. Available at
http://sourceforge.net/projects/smolder
Smolder is a Open Source Perl smoke test aggregator used primarily to collect
the results of automated test runs and distribute those to users.
An introduction is given in my slides from the
Chris Dolan wrote:
On Sep 24, 2006, at 5:42 PM, Christopher H. Laco wrote:
Ok, I'll play your game. :-)
http://perlcritic.tigris.org/svn/perlcritic/trunk/Perl-Critic/lib/Perl/Critic/Policy/Testing/
[Assuming I'm not silly] Empty! Rev. 667
-=Chris
D'oh! SVN commits work better if
On Sep 25, 2006, at 8:16 PM, Christopher H. Laco wrote:
Now, for part 2. :-)
What's the sanest way to test t/*.t files without also testing
everything in t/lib ?
If I'm already using all_critic_ok(), I can't just call critic_ok() on
all the t/*.t files because a plan has already been set.
On 22 Sep 2006, at 09:11, Ovid wrote:
I don't have time to track this down, but I've noticed the
following when I run my Test::Class tests through prove:
[snip]
As you may notice, you see the diagnostics from the TODO failures.
As Schwern has noted repeatedly:
The user should not
14 matches
Mail list logo
