On Sun, 18 Feb 2001 [EMAIL PROTECTED] wrote:
> If anyone else would be willing to become a smoker, please step
> forward. I'm requesting that Ask set up [EMAIL PROTECTED] (aka The
> Smoker's Lounge) for further discussion. I'll let everyone know when
> its up.
I'm addicted already. I don't ha
On Sun, Feb 18, 2001 at 09:22:00PM -0800, Richard Soderberg wrote:
> I'm addicted already. I don't have the daylight time to put energy into
> doing huge amounts of set up on my local machine, but if you have a script
> that'll do what you need, I've got a CPU just resting here doing nothing.
We
On Mon, Feb 19, 2001 at 05:34:49AM +0100, Andreas J. Koenig wrote:
> > On Sun, 18 Feb 2001 16:08:49 -0500, [EMAIL PROTECTED] (Michael G. Schwern)
>said:
>
> > On Sun, Feb 18, 2001 at 07:20:55PM +, [EMAIL PROTECTED] wrote:
> >> <[EMAIL PROTECTED]> writes:
> >> >Why is t/TEST anyth
> On Sun, 18 Feb 2001 16:08:49 -0500, [EMAIL PROTECTED] (Michael G. Schwern) said:
> On Sun, Feb 18, 2001 at 07:20:55PM +, [EMAIL PROTECTED] wrote:
>> <[EMAIL PROTECTED]> writes:
>> >Why is t/TEST anything more than a thin wrapper around Test::Harness?
>>
>> Because t/TEST pre-
On Sun, Feb 18, 2001 at 06:26:00PM -0500, [EMAIL PROTECTED] wrote:
> I'd like to set up automated daily build and smoke tests for bleedperl
> and the other active trees.
How many configuration permutations were you proposing?
> It will be fairly simple to write and distribute a cron job which
>
On Sun, 18 Feb 2001 [EMAIL PROTECTED] wrote:
> On Sun, Feb 18, 2001 at 07:20:55PM +, [EMAIL PROTECTED] wrote:
> > <[EMAIL PROTECTED]> writes:
> > >Why is t/TEST anything more than a thin wrapper around Test::Harness?
> >
> > Because t/TEST pre-dates Test::Harness by years, and no one has got
On Sun, Feb 18, 2001 at 06:14:05PM -0500, Andy Dougherty wrote:
> > Would anyone scream if I gave a shot at gutting TEST?
>
> Please make sure 'make minitest' works.
Check. I'd forgotten about it.
> And also think about what happens if 'use' is broken :-).
Bad things, Mikey. Bad things.
S
If anyone's not familiar, a daily build and smoke test is the practice
of building the entire system and running its tests every night to see
if anything was broken durning the day's work. Turn it on, see if it
smokes. This reduces the scope of bugs and keeps things from
festering. You know the
[EMAIL PROTECTED] wrote:
> If anyone else would be willing to become a smoker, please step
> forward. I'm requesting that Ask set up [EMAIL PROTECTED] (aka The
> Smoker's Lounge) for further discussion. I'll let everyone know when
> its up.
I have 3 identical Ultra1 machines running Solaris 2.
On Sun, Feb 18, 2001 at 11:33:52PM +, Nicholas Clark wrote:
> On Sun, Feb 18, 2001 at 06:26:00PM -0500, [EMAIL PROTECTED] wrote:
> > I'd like to set up automated daily build and smoke tests for bleedperl
> > and the other active trees.
>
> How many configuration permutations were you proposin
I'd like to set up automated daily build and smoke tests for bleedperl
and the other active trees.
If anyone's not familiar, a daily build and smoke test is the practice
of building the entire system and running its tests every night to see
if anything was broken durning the day's work. Turn it
On Sat, Feb 17, 2001 at 10:44:44PM -0500, [EMAIL PROTECTED] wrote:
> On Sat, Feb 17, 2001 at 09:08:15PM -0600, Jarkko Hietaniemi wrote:
> > I think it was supposed to be TEST with -Mutf8, basically.
> > Why it was a separate script? Beats me.
>
> Well, its not anymore. I've added a -utf8 flag t
On Sun, Feb 18, 2001 at 01:48:50AM -0500, [EMAIL PROTECTED] wrote:
> A few weeks ago I brought up the idea of unifying the format of todo
> tests and skip tests:
> http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2001-01/msg00883.html
>
> Well, here it is. This is a patch to both t/TEST an
On Sat, Feb 17, 2001 at 10:05:30PM -0500, [EMAIL PROTECTED] wrote:
> And what the hell is t/UTEST? Looks like its for unicode. Ok, fine,
I think it was supposed to be TEST with -Mutf8, basically.
Why it was a separate script? Beats me.
> but I don't like the code duplication. In fact, it alr
On Sat, Feb 17, 2001 at 10:22:13AM -0600, Jarkko Hietaniemi wrote:
> > One additional point to consider and solve is the BEGIN 'preamble' we
> > now add to each test to make certain we are in a known directory, and
> > more importantly, that we are running the tests using *the* lib/ of
> > the Per
> One additional point to consider and solve is the BEGIN 'preamble' we
> now add to each test to make certain we are in a known directory, and
> more importantly, that we are running the tests using *the* lib/ of
> the Perl we are building and not some other lib. Having to add that
> preamble ma
> Fortunately, this is a fairly rote process. Unfortunately, its not
> easily automatable since the current test naming scheme is
> inconsistant. Also, some tests rely on their name being what it is.
> No worries, though, this can be done as an incremental process.
>
> Thought... we might want
On Sun, Feb 18, 2001 at 07:20:55PM +, [EMAIL PROTECTED] wrote:
> <[EMAIL PROTECTED]> writes:
> >Why is t/TEST anything more than a thin wrapper around Test::Harness?
>
> Because t/TEST pre-dates Test::Harness by years, and no one has got
> round to changing 'make test' call the new style.
I
<[EMAIL PROTECTED]> writes:
>Why is t/TEST anything more than a thin wrapper around Test::Harness?
Because t/TEST pre-dates Test::Harness by years, and no one has got
round to changing 'make test' call the new style.
>It contains a partial reimplementation, but is missing some very
>useful feat
Carp has almost no explicit coverage in the core tests. Now, before I
go ahead and write up a test, does anyone have some old tests lying
around from the Olden Days of Yore?
As discussed eariler in
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2001-02/msg00908.html
I've added t/TestSetup.pm and made t/TEST use it. I had to be careful
to do "-I. -MTestSetup" or else modules which used taint would not work.
A few tests which used do EXPR assumed that '.' wo
On Sun, Feb 18, 2001 at 10:39:54AM +0100, Andreas J. Koenig wrote:
> Thanks! I've registered you as maintainer on PAUSE, so that the
> indexer will pick your uploads of Test::Harness in the usual way.
I had a feeling you'd be all too eager to get it off your hands. ;)
I've looked at Test::Harnes
Thanks! I've registered you as maintainer on PAUSE, so that the
indexer will pick your uploads of Test::Harness in the usual way.
--
andreas
23 matches
Mail list logo
