On 10/6/07, David Cantrell <[EMAIL PROTECTED]> wrote:
> Every single report that I sent since the beginning of last month that
> was over 40K included verbose errors (including warnings) of some kind
> or another, even the PASSes. I didn't look particularly hard at test
> reports below 40K.
I whi
On 10/6/07, David Cantrell <[EMAIL PROTECTED]> wrote:
> On Sat, Oct 06, 2007 at 04:59:21PM -0400, David Golden wrote:
> > (b) plenty of modules test warnings by sending stuff to STDERR.
> > (Probably shouldn't but they do.)
>
> They not only shouldn't, but simply printing to STDERR to test somethin
On Sat, Oct 06, 2007 at 04:59:21PM -0400, David Golden wrote:
> (b) plenty of modules test warnings by sending stuff to STDERR.
> (Probably shouldn't but they do.)
They not only shouldn't, but simply printing to STDERR to test something
to do with warnings is a bug. To test a warning, you need t
On 10/6/07, David Cantrell <[EMAIL PROTECTED]> wrote:
> It wouldn't be the first time a module had had OS-specific features. In
> this case, "if you're on Unix you can ...".
CPAN::Reporter already uses Win32::Process when it needs to honor CPAN
interactivity_timeout requests. (Which I do plan to
Barbie wrote:
> On Fri, Oct 05, 2007 at 08:46:13AM -0400, David Golden wrote:
>> I might be able to build that kind of a kill as a parameter to Tee --
>> if the tee file exceeds a certain size, then kill the process. But
>> even that might require some real work to be portable. Forks and
>> timeo
David Golden wrote:
> On 10/5/07, David Landgren <[EMAIL PROTECTED]> wrote:
>> David Cantrell wrote:
>>> From a quick look over the reports I've sent this month, 40K looks like
>>> a good cutoff point. Add the introductory text, perl -V, and any
>>> comments I might add by hand, and it'll still be
On 10/5/07, Barbie <[EMAIL PROTECTED]> wrote:
> Unfortunately this would require a change to CPANPLUS (and probably
> CPAN/CPAN-Reporter) to capture the output rather than just create a
> simple PASS report.
It's worse -- you need to capture STDERR while trying to maintain the
order of STDOUT and
On Fri, Oct 05, 2007 at 08:46:13AM -0400, David Golden wrote:
> On 10/5/07, David Landgren <[EMAIL PROTECTED]> wrote:
> > David Cantrell wrote:
> > > From a quick look over the reports I've sent this month, 40K looks like
> > > a good cutoff point. Add the introductory text, perl -V, and any
> > >
On 10/5/07, David Landgren <[EMAIL PROTECTED]> wrote:
> David Cantrell wrote:
> > From a quick look over the reports I've sent this month, 40K looks like
> > a good cutoff point. Add the introductory text, perl -V, and any
> > comments I might add by hand, and it'll still be well under 50K.
>
> Ag
David Cantrell wrote:
On Thu, Oct 04, 2007 at 02:09:01PM -0400, David Golden wrote:
From a quick look over the reports I've sent this month, 40K looks like
a good cutoff point. Add the introductory text, perl -V, and any
comments I might add by hand, and it'll still be well under 50K.
Agree
On Thu, Oct 04, 2007 at 02:09:01PM -0400, David Golden wrote:
> Slaven Rezic has figured out that some test reports are exceeding the
> 400K maximum size that develooper.com will accept. It seems
> reasonable to truncate the test output included. (Maybe long term
> gzip and attach instead.)
I'v
Slaven Rezic has figured out that some test reports are exceeding the
400K maximum size that develooper.com will accept. It seems
reasonable to truncate the test output included. (Maybe long term
gzip and attach instead.)
400K seems like a lot. Ask has suggested it be smaller, but hasn't
specifi
12 matches
Mail list logo
