develooper Front page | perl.perl5.porters | Postings from January 2006

Re: Smoke [5.8.8] 26944 FAIL(F) openvms V8.2 (Alpha/1 cpu)

Thread Next
From:
Nicholas Clark
Date:
January 26, 2006 11:54
Subject:
Re: Smoke [5.8.8] 26944 FAIL(F) openvms V8.2 (Alpha/1 cpu)
Message ID:
20060126195417.GN616@plum.flirble.org
On Thu, Jan 26, 2006 at 08:19:00AM -0600, craigberry@mac.com wrote:
> Automated smoke report for 5.8.8 patch 26944
> BRIANA: Digital Personal WorkStation  (Alpha/1 cpu)
>     on        openvms - V8.2
>     using     CC/DECC version 70190015
>     smoketime 9 hours 23 minutes (average 4 hours 41 minutes)
> 
> Summary: FAIL(F)

Thanks for this smoke report

>     [-.ext.Devel.PPPort.t]ppphtest.t........FAILED 2-8 11-14 17
                                              ...
>     [-.ext.List.Util.t]p_tainted.t..........FAILED ??
>     [-.lib.ExtUtils.t]PL_FILES.t............FAILED 3-7
>     [-.lib.ExtUtils.t]basic.t...............FAILED 67 69 71 74
>     [-.lib.File]Copy.t......................FAILED 20
>     io/crlf_through.t.......................FAILED 4-6 13-14 17
                                              ...
>     io/fs.t.................................FAILED 5
>     io/through.t............................FAILED 4-6 13-14 17
                                              ...
>     op/cmp.t................................FAILED 43-7854
>     op/goto.t...............................FAILED 53-54
>     pod/pod2usage2.t........................FAILED 2-3 5-13 15

Whilst I'm aware that these are all fixed now in blead, I don't know the
minimal set of specific changes needed to integrate to fix them, and in
turn whether they have dependencies on things I didn't want to integrate
yet, such as the exit handling macros, or updates to dual life modules not
yet released to CPAN.

On the assumption that not all can be fixed with small, VMS specific changes
(and that I don't have the knowledge to work out what those small changes
would be) I feel that I'd prefer to ship 5.8.8 with an note in the perldelta
that VMS is failing tests, and get everything fixed up for 5.8.9.

5.8.8 is too late already (my fault), and I'd prefer it not to become even
later. I don't intend to let 5.8.9 slip. My plan is not to repeat what
happened with 5.8.7 and 5.8.8, and to re-start merging things to maint soon
after 5.8.8 ships.

Nicholas Clark

Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About