> On Sat, 17 Oct 2009 00:18:16 +0300, Burak Gürsoy
> said:
> Hello dcollins and anyone using some must-be-obliterated blead perl version
for testing,
> Can you please stop testing with 5.9.x as this does not have any meaning as
of today (or as of today 2 years ago). I'm sending thi
Hello dcollins and anyone using some must-be-obliterated blead perl version for
testing,
Can you please stop testing with 5.9.x as this does not have any meaning as of
today (or as of today 2 years ago). I'm sending this request because I got a
confusing/non-sensical FAIL from an old developer
Hi. wheel_readline for select or io_poll seems to fail for cygwin,
with either 5.8.8 or 5.10.0 for POE 1.280, 1.269, 1.268.
I would like to help fix this, but the tests seem to be sophisticated,
and even looking at poe-gen-tests I am stumped.
What can be done? Should the test be skipped on cygw
2009/10/16 David Golden
> Current minimum targets:
>
> 'Test::Reporter' => 1.54,
> 'CPAN::Reporter' => 1.1708,
> 'CPANPLUS'=> 0.8601,
>
That's precisely what I have:
'Test::Reporter' => 1.54,
'CPAN::Reporter' => 1.1708,
'CPAN' => 1.9402
So this means that truncation cannot explain why almost all of my test
reports from last week disappeared:
I installed Test::Reporter and CPAN::Reporter only days before sending, so
they should be up to date.
But maybe perl.org's blackhole really was the cause.
> On Fri, Oct 16, 2009 at 10:31 AM,
On Fri, Oct 16, 2009 at 10:50 AM, Barbie wrote:
> Hi folks,
>
> If you are using CPAN-Reporter to run your smoke severs, please can you
> ensure you have the latest, or at least version 1.1706 or greater, as
> there are still several reports being submitted with unsupported URLs to
> the CPAN Test
On Fri, Oct 16, 2009 at 10:48:49AM -0400, David Golden wrote:
> On Fri, Oct 16, 2009 at 10:31 AM, Barbie wrote:
> > Not necessarily. If the report exceeds the byte limit it gets truncated.
> > All the perl -V data is at the end, which is the primary source of
> > discovery for the perl version. No
Hi folks,
If you are using CPAN-Reporter to run your smoke severs, please can you
ensure you have the latest, or at least version 1.1706 or greater, as
there are still several reports being submitted with unsupported URLs to
the CPAN Testers eco-system.
Cheers,
Barbie.
--
Birmingham Perl Mongers
On Fri, Oct 16, 2009 at 10:31 AM, Barbie wrote:
> Not necessarily. If the report exceeds the byte limit it gets truncated.
> All the perl -V data is at the end, which is the primary source of
> discovery for the perl version. Note this is a limit of the NNTP mail
> server, and one reason why we wa
Hi Steffen,
> Just an intermediate update:
>
> Some of the test reports I sent yesterday night are already visible, others
> not (why?).
>
> In particular, I sent:
>
> # Generated by CPAN::Reporter 1.1708
> test PASS Carp-Clan-6.00 (perl-5.10.1) MSWin32-x86-multi-thread 5.1
> test PASS Bit-Vect
Just an intermediate update:
Some of the test reports I sent yesterday night are already visible, others
not (why?).
In particular, I sent:
# Generated by CPAN::Reporter 1.1708
test PASS Carp-Clan-6.00 (perl-5.10.1) MSWin32-x86-multi-thread 5.1
test PASS Bit-Vector-7.1 (perl-5.10.1) MSWin32-x86-
Barbie writes:
> On Thu, Oct 15, 2009 at 06:32:57PM -0400, M W487 wrote:
>> Basically at random, I decided to track some reports I have sent and
>> see how they turn up. Most look good. Here is a possible problem:
>>
>> http://www.nntp.perl.org/group/perl.cpan.testers/2009/10/msg5477314.html
>
12 matches
Mail list logo
