[Info-vax] Perl 5.28.1 binary kit for OpenVMS I64 available
Craig A. Berry
craigberry at nospam.mac.com
Wed Dec 5 06:47:05 EST 2018
On 12/4/18 1:02 AM, Joukj wrote:
> Craig A. Berry wrote:
>> On 11/29/18 7:07 PM, John H. Reinhardt wrote:
>>> On 11/29/2018 6:29 PM, Craig A. Berry wrote:
>>>> An installation kit for OpenVMS I64 v8.4 and later is available at:
>>>>
>>>> <https://sourceforge.net/projects/vmsperlkit/files/>
>>>>
>>>> N.B. I no longer have working Alpha hardware so there is no Alpha kit.
>>>>
>>>
>>> I have an XP1000 and a DS10. What does it take to build the kit like
>>> you used to for distribution? Do you have canned build DCL scripts?
>>
>> The procedures to build the kits are all part of the same project from
>> which I distribute the kits:
>>
>> <https://sourceforge.net/p/vmsperlkit/code/ci/default/tree/perlkit/>
>>
>
> I tried this on both Alpha and IA64. It even created a PCSI-kit.
>
> but.,,,, Then I gave the following command in the [.source] directory:
> $ MMK test
>
> This resulted in 19 failed tests on Alpha and 20 on IA64 (see details
> below). Is this "normal" behaviour? and if so why are these tests not
> skipped like so many other tests?
I usually get 2 or 3 test failures on my systems for things I haven't
gotten around to fixing. Never anywhere near what you got. There could
be be many possible explanations about what's different in your
environment, from DECC$* settings, to volume characteristics, to whether
networking tests can find a network to test with.
The first thing I would try to eliminate would be testing with
privileges enabled, for example by having a system UIC group (what is
it, 010 or lower?). The test suite explicitly downgrades its privileges,
but that won't help if you are running under a system account. There are
quite a few tests that try to make sure there are certain things they
cannot do -- if they end up being able to do them because of elevated
privileges, the test fails.
Other than that, each test would have to be run individually and
debugged to see what differs between what it's getting and what it's
expecting.
But you did get 99.2% OK, so you likely have pretty high-functioning
Perl kits.
>
> On Alpha I get:
>
> Failed 19 tests out of 2368, 99.20% okay.
> ../cpan/Archive-Tar/t/04_resolved_issues.t
> ../cpan/ExtUtils-Install/t/Install.t
> ../cpan/ExtUtils-Install/t/InstallWithMM.t
> ../cpan/ExtUtils-Install/t/Installapi2.t
> ../cpan/ExtUtils-Install/t/can_write_dir.t
> ../cpan/ExtUtils-MakeMaker/t/02-xsdynamic.t
> ../cpan/ExtUtils-MakeMaker/t/INSTALL_BASE.t
> ../cpan/ExtUtils-MakeMaker/t/PL_FILES.t
> ../cpan/ExtUtils-MakeMaker/t/basic.t
> ../cpan/ExtUtils-MakeMaker/t/miniperl.t
> ../cpan/ExtUtils-MakeMaker/t/pm_to_blib.t
> ../cpan/ExtUtils-MakeMaker/t/unicode.t
> ../cpan/File-Path/t/Path.t
> ../cpan/Test-Harness/t/proverun.t
> ../ext/POSIX/t/posix.t
> ../ext/Pod-Html/t/cache.t
> ../lib/perl5db.t
> io/fs.t
> op/stat.t
> ### Since not all tests were successful, you may want to run some of
> ### them individually and examine any diagnostic messages they produce.
> ### See the INSTALL document's section on "make test".
> ### You have a good chance to get more information by running
> ### ./perl harness
> ### in the 't' directory since most (>=80%) of the tests succeeded.
> Elapsed: 17560 sec
> u=590.67 s=0.00 cu=0.00 cs=0.00 scripts=2368 tests=998630
>
>
>
> On IA64 I get:
>
> Failed 20 tests out of 2367, 99.16% okay.
> ../cpan/Archive-Tar/t/04_resolved_issues.t
> ../cpan/ExtUtils-Install/t/Install.t
> ../cpan/ExtUtils-Install/t/InstallWithMM.t
> ../cpan/ExtUtils-Install/t/Installapi2.t
> ../cpan/ExtUtils-Install/t/can_write_dir.t
> ../cpan/ExtUtils-MakeMaker/t/02-xsdynamic.t
> ../cpan/ExtUtils-MakeMaker/t/INSTALL_BASE.t
> ../cpan/ExtUtils-MakeMaker/t/PL_FILES.t
> ../cpan/ExtUtils-MakeMaker/t/basic.t
> ../cpan/ExtUtils-MakeMaker/t/miniperl.t
> ../cpan/ExtUtils-MakeMaker/t/pm_to_blib.t
> ../cpan/ExtUtils-MakeMaker/t/unicode.t
> ../cpan/File-Path/t/Path.t
> ../cpan/Test-Harness/t/proverun.t
> ../ext/POSIX/t/posix.t
> ../ext/Pod-Html/t/cache.t
> ../lib/perl5db.t
> io/fs.t
> io/socket.t
> op/stat.t
> ### Since not all tests were successful, you may want to run some of
> ### them individually and examine any diagnostic messages they produce.
> ### See the INSTALL document's section on "make test".
> ### You have a good chance to get more information by running
> ### ./perl harness
> ### in the 't' directory since most (>=80%) of the tests succeeded.
> Elapsed: 5809 sec
> u=270.59 s=0.00 cu=0.00 cs=0.00 scripts=2367 tests=998647
More information about the Info-vax
mailing list