Michael G Schwern said:
The problem I'm hearing over and over again is Test::Builder is spewing
crap all over my screen and obscuring the first, real failure. So now
that the problem is clearly stated, how do we solve it without making
all that spew (which can be useful) totally
--- Salve J Nilsen [EMAIL PROTECTED] wrote:
Ok, a shot in the dark...
1. Redirect test output to a temporary log file (which should get
cleaned
up during make clean al.)
2. Let the harness be aware of this log file, and tail(1) it as
things
get written to it, printing whatever's
On Fri, Jan 11, 2008 at 06:12:57PM -0800, Roman Shaposhnik wrote:
My main beef with stack helpers is that they have to be executed
inside the kernel and are subject to the usual DTrace restrictions.
I would like to see a possibility of offloading more work to user
space in a generic
On Jan 12, 2008, at 12:26 PM, Adam Leventhal wrote:
On Fri, Jan 11, 2008 at 06:12:57PM -0800, Roman Shaposhnik wrote:
My main beef with stack helpers is that they have to be executed
inside the kernel and are subject to the usual DTrace restrictions.
I would like to see a possibility of
Ovid said:
--- Salve J Nilsen [EMAIL PROTECTED] wrote:
Ok, a shot in the dark...
1. Redirect test output to a temporary log file (which should get
cleaned up during make clean al.)
2. Let the harness be aware of this log file, and tail(1) it as
things get written to it, printing
Smylers wrote:
Names normally descend in specificity from left to right, but
Test::More::Even doesn't really make sense.
How about Test::More::Still, Test::More::Stuff, Test::More::Crap,
Test::More::More :)
--
Michael Peters
Developer
Plus Three, LP
--- Smylers [EMAIL PROTECTED] wrote:
Ovid writes:
Forget all the silly debates. I don't want to wait or sit around
while we argue over this silly stuff.
You mean you don't want flaming for the apostrofly in the subject?
OK then, I won't mention it.
Yeah, I saw that right after I
Let me know if there are any problems. I'm sure there will be :)
Cheers,
Ovid
--- PAUSE [EMAIL PROTECTED] wrote:
Date: Sun, 13 Jan 2008 18:07:17 +0100
Subject: CPAN Upload: O/OV/OVID/Test-Most-0.01.tar.gz
To: Curtis Ovid Poe [EMAIL PROTECTED]
From: PAUSE [EMAIL PROTECTED]
The uploaded
Matisse Enzer wrote:
On Jan 12, 2008, at 10:24 PM, Michael G Schwern wrote:
Matisse Enzer wrote:
I just want to be able to run a test suite with a switch that makes the
entire test run stop after the first failure is reported.
Ok, it's nice to want things, but why do you want it?
--- Ovid [EMAIL PROTECTED] wrote:
Let me know if there are any problems. I'm sure there will be :)
For those who can't wait, the docs are at
http://use.perl.org/~Ovid/journal/35381.
I forgot to credit Smylers with the name in the CPAN version. This
will be corrected in the next release.
On Jan 13, 2008, at 9:17 AM, Michael G Schwern wrote:
Matisse Enzer wrote:
On Jan 12, 2008, at 10:24 PM, Michael G Schwern wrote:
Matisse Enzer wrote:
I just want to be able to run a test suite with a switch that
makes the
entire test run stop after the first failure is reported.
Ok,
Michael G Schwern wrote:
Ok, why do you want to stop it as fast as possible when a failure occurs?
I have a 45 minute test suite and I want to work on the first failure as soon as
possible. I also have multiple desktops and am doing other things in another
desktop, so I want to know as soon as
On 13 Jan 2008, at 18:06, Michael Peters wrote:
Ok, why do you want to stop it as fast as possible when a failure
occurs?
I have a 45 minute test suite and I want to work on the first
failure as soon as
possible. I also have multiple desktops and am doing other things in
another
desktop,
On Sunday 13 January 2008 04:27:38 Ovid wrote:
--- Salve J Nilsen [EMAIL PROTECTED] wrote:
1. Redirect test output to a temporary log file (which should get
cleaned up during make clean al.)
2. Let the harness be aware of this log file, and tail(1) it as
things get written to it,
Michael Peters wrote:
Michael G Schwern wrote:
Ok, why do you want to stop it as fast as possible when a failure occurs?
I have a 45 minute test suite and I want to work on the first failure as soon
as
possible. I also have multiple desktops and am doing other things in another
desktop,
On Jan 13, 2008, at 10:40 AM, Michael G Schwern wrote:
You see how this is distinct from halt on first failure? It gives
me a lot
more room for different solutions that don't involve just cutting
off all the
following information.
I do see (and respect) that difference, but stopping
Michael G Schwern wrote:
Paul Johnson wrote:
This is something that I too have asked for in the past. I've even
hacked up my own stuff to do it, though obviously not as elegantly as
you or Geoff. Here's my use case.
I have a bunch of tests that generally pass. I hack something
fundamental
Adam Kennedy wrote:
This shouldn't be any more complicated than -g (where g in my case
stands for goat as in feinting goat)
Ok, I'll bite. Why a goat and why is it feinting?
--
...they shared one last kiss that left a bitter yet sweet taste in her
mouth--kind of like throwing up after
* Michael G Schwern [EMAIL PROTECTED] [2008-01-14 00:35]:
Why a goat and why is it feinting?
Because http://video.google.com/videoplay?docid=5306665151934403100
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
# from Smylers
# on Sunday 13 January 2008 04:29:
Names normally descend in specificity from left to right, but
Test::More::Even doesn't really make sense.
I'm glad Test::More::Better got missed. I call dibs.
--Eric
--
So malloc calls a timeout and starts rummaging around the free chain,
* Eric Wilhelm [EMAIL PROTECTED] [2008-01-14 03:15]:
I'm glad Test::More::Better got missed. I call dibs.
Test::More::Better::Bigger::Badder?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
Aristotle Pagaltzis wrote:
* Eric Wilhelm [EMAIL PROTECTED] [2008-01-14 03:15]:
I'm glad Test::More::Better got missed. I call dibs.
Test::More::Better::Bigger::Badder?
Regards,
Test::More::Bigger::Longer::Uncut
signature.asc
Description: OpenPGP digital signature
# from chromatic
# on Sunday 13 January 2008 10:28:
How is this simpler than 'bail on fail' or 'die on fail'?
It doesn't conflate output TAP results from tests with interpret
TAP results from tests.
Yes.
--
I arise in the morning torn between a desire to improve the world and a
desire to
Matisse Enzer wrote:
Ok, why do you want to stop it as fast as possible when a failure
occurs?
So I can more quickly focus on fixing that first test failure.
I use
make test 21 | less
Works for individual tests too
make perl -Mblib t/testname.t 21 | less
Sam.
I know I am a bit late to the party but what about Test::Anything ?
Gabor
On Jan 13, 2008, at 7:13 PM, Sam Vilain wrote:
Matisse Enzer wrote:
Ok, why do you want to stop it as fast as possible when a failure
occurs?
So I can more quickly focus on fixing that first test failure.
I use
make test 21 | less
Works for individual tests too
make perl -Mblib
26 matches
Mail list logo
