maint-5.10 status on VMS
I've finally got Test::Smoke mostly working on VMS except for my local
mail configuration, thus the manual attachment here. It shows the
only failures I've seen recently:
lib/ExtUtils/t/
Installapi2FAILED at test 15
lib/ExtUtils/t/
InstallFAILED at test 15
which started happening occasionally (but not consistently) after
Yves' recent changes to ExtUtils::Install. When I run these tests
individually they usually (though not always) fail once and then
succeed when run again. The test that fails is the same in both
scripts and looks like:
install( { 'blib/lib' = 'install-test/lib/perl',
read = 'install-test/packlist',
write = 'install-test/packlist'
},
0, 1);
ok( ! -d 'install-test/lib/perl','install made dir (dry run)');
So it's testing for the non-existence of a directory that should not
be there because we only did a dry run. The most likely explanation
is something is not getting cleaned up properly elsewhere so we are
finding something we shouldn't. So far I have not been able to spot
why the fairly minimal recent changes would cause that, but I'll keep
looking.
Craig A. Berry
mailto:craigbe...@mac.com
... getting out of a sonnet is much more
difficult than getting in.
Brad Leithauser
Automated smoke report for 5.10.1 patch
836440f600bbb4a6dc8bb661536f81681032312a maint-5.10-1622-g836440f
ALMA: HP rx2600 (1.50GHz/6.0MB) (IA64/2 cpu)
onopenvms - V8.3-1H1
using ? CC/DECC version 70390018
smoketime 3 hours 45 minutes (average 1 hour 52 minutes)
Summary: FAIL(F)
O = OK F = Failure(s), extended report at the bottom
X = Failure(s) under TEST but not under harness
? = still running or test results not (yet) available
Build failures during: - = unknown or N/A
c = Configure, m = make, M = make (after miniperl), t = make test-prep
maint-5.10-1622-g836440f Configuration (common) none
--- -
F -
F - -Duseithreads
| +- -DDEBUGGING
+--- no debugging
Locally applied patches:
SMOKE836440f600bbb4a6dc8bb661536f81681032312a
Failures: (common-args) none
[default]
lib/ExtUtils/t/InstallFAILED at
test 15
23-JUL-2009 19:32:53.37 User: SMOKEProcess ID: 00025279
[default] -Duseithreads
lib/ExtUtils/t/Installapi2FAILED at
test 15
lib/ExtUtils/t/InstallFAILED at
test 15
23-JUL-2009 21:32:34.93 User: SMOKEProcess ID: 00027193
--
Report by Test::Smoke v1.39 build 1235 running on perl 5.10.0
(Reporter v0.035 / Smoker v0.044)
smoking VMS (was Re: maint-5.10 status on VMS)
On Fri, Jul 24, 2009 at 03:35:33PM -0500, Craig A. Berry wrote: I've finally got Test::Smoke mostly working on VMS except for my local mail configuration, thus the manual attachment here. It shows the Ooh. ooh. ooh. ooh. What will it take to get the mail bit sorted, so that it can run automatically? And run automatically on blead too? Nicholas Clark
Re: VMS::Persona
Peter Prymmer/FactSet wrote on 07/22/2009 12:30:14 PM: I may be able to issue a patch to get the $VMS::Persona::VERSION == 1.01 building against perl 5.8.7 on Alpha It could take me a bit of time though (so do not hold your breathe). OK - you can start breathing again ;-) It sounds like Carl already has the s/na/PL_na/ stuff already taken care of. Nevertheless other folks on this list may still be interested in the content of this patch (see attachement). I note the following items regarding a successful run of mmk test (or mms test): 1. it must be run from a process with elevated privs to be successful 2. it must be run from an account other than SYSTEM (although now it is not necessary to have an ORACLE user to run this test, merely someone other than SYSTEM). This worked for us on Alpha, but we do not use it on our Itanium perl installations. I hope it proves helpful to you Carl and anyone else who might want to try it. Peter Prymmer persona.patch Description: Binary data
RE: VMS::Persona
Peter, (so do not hold your breathe). OK - you can start breathing again ;-) It sounds like Carl already has the s/na/PL_na/ stuff already taken care of. Nevertheless other folks on this list may still be interested in the content of this patch (see attachement). I note the following items regarding a successful run of mmk test (or mms test): 1. it must be run from a process with elevated privs to be successful 2. it must be run from an account other than SYSTEM (although now it is not necessary to have an ORACLE user to run this test, merely someone other than SYSTEM). This worked for us on Alpha, but we do not use it on our Itanium perl installations. I hope it proves helpful to you Carl and anyone else who might want to try it. Thanks, Peter. I won't be able to get to this right away, but I do want to try it. Looks like you cleaned up the tests, that's great. What version (s) of perl and VMS? Best wishes, Carl Friedberg friedb...@comets.com www.comets.com
Re: smoking VMS (was Re: maint-5.10 status on VMS)
On Jul 24, 2009, at 3:40 PM, Nicholas Clark wrote: On Fri, Jul 24, 2009 at 03:35:33PM -0500, Craig A. Berry wrote: I've finally got Test::Smoke mostly working on VMS except for my local mail configuration, thus the manual attachment here. It shows the Ooh. ooh. ooh. ooh. What will it take to get the mail bit sorted, so that it can run automatically? And run automatically on blead too? I've run it successfully with both blead and maint, and I've implemented support in Test::Smoke for the native VMS mail utility and successfully sent myself smoke reports with it. One approach to getting mail to places it needs to go would be to subscribe to one or another perl.org mailing list with the account on each machine that will be generating smoke reports (these are on my home network and I don't normally use them for e-mail). Another approach would be to add support to Test::Smoke to use MIME::Lite's authentication features and send via an external smtp server, though that would involve leaving a password sitting around in clear text. Bram has now suggested a third possibility, which is interesting. I will now go and read the Test::Smoke FAQ and find out what I'm supposed to be doing :-). Oh, and you used the word automatically, which still needs some work. I'm currently running rsync on Mac OS X in order to get the .patch file so we know what we're smoking, then generating a zipball and moving it to ~/Sites, then kicking off a job on the VMS side that uses curl to pull it across and run the smoke test. When a tuit or two present themselves, there are lots of different approaches to coordinating and automating all of this. _ Craig A. Berry mailto:craigbe...@mac.com ... getting out of a sonnet is much more difficult than getting in. Brad Leithauser
Re: smoking VMS (was Re: maint-5.10 status on VMS)
Craig A. Berry wrote: On Jul 24, 2009, at 3:40 PM, Nicholas Clark wrote: On Fri, Jul 24, 2009 at 03:35:33PM -0500, Craig A. Berry wrote: I've finally got Test::Smoke mostly working on VMS except for my local mail configuration, thus the manual attachment here. It shows the Ooh. ooh. ooh. ooh. What will it take to get the mail bit sorted, so that it can run automatically? And run automatically on blead too? I've run it successfully with both blead and maint, and I've implemented support in Test::Smoke for the native VMS mail utility and successfully sent myself smoke reports with it. One approach to getting mail to places it needs to go would be to subscribe to one or another perl.org mailing list with the account on each machine that will be generating smoke reports (these are on my home network and I don't normally use them for e-mail). Another approach would be to add support to Test::Smoke to use MIME::Lite's authentication features and send via an external smtp server, though that would involve leaving a password sitting around in clear text. Bram has now suggested a third possibility, which is interesting. I will now go and read the Test::Smoke FAQ and find out what I'm supposed to be doing :-). Oh, and you used the word automatically, which still needs some work. I'm currently running rsync on Mac OS X in order to get the .patch file so we know what we're smoking, then generating a zipball and moving it to ~/Sites, then kicking off a job on the VMS side that uses curl to pull it across and run the smoke test. When a tuit or two present themselves, there are lots of different approaches to coordinating and automating all of this. I can supply you with a GIT program that can clone a repository. I can not get the other functions working for a while due to limitations in the GNV ports of several utilities and some other problems. If you (or anyone else) wishes to pursue that, drop a mail on the vms-perl list and I will respond with the details. I do not know if the clone function can pull down a specific branch. It is also pretty slow. It takes at least 1/2 for the git clone to pull down Perl on my DS-10. -John wb8...@qsl.net Personal Opinion Only
