> -----Original Message-----
> From: Craig A. Berry [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, September 22, 2002 4:15 PM
> To: Henderson, Jordan
> Cc: 'Vmsperl (E-mail)'
> Subject: test builds (was RE: Building 5.8.0 problem)
>
>
> At 5:01 PM -0400 9/19/02, Henderson, Jordan wrote:
>
> > It
> >occurs to me that I'm in a good position to smoke test perl
> builds here. I
> >think I have access to at least 6 and possibly more
> different combinations of
> >OS's, C compilers and MMS/MMK. Hmmm... We will be upgrading
> those 7.1 systems
> >soon, so we'll be back to 5 or more. Now that I think of
> it, I only have 3 or 4
> >that really wouldn't attract any attention if I ran
> something like this. The
> >developers on the other configurations might complain about
> such a use.
>
> Unless the developers stay up 24 hours a day, there's no reason to
> build while they are working. Of course they may have there own
> build jobs that run overnight.
You would think, but these people are very protective of their machines...
And, they're likely to be running 24x7 testing with a parallel feed of
production data at just any time. If they feel that there is any way that
other uses for these machines _might_ impact their testing, they'll shut me
down.
Discretion, valor, etc.
>
> >Only VAX I have access to these days is one I have turned
> off at home, though.
> >:-(
>
> I'm sure there are those here who, if supplied the exact model number
> and configuration details, could offer appropriate advice on locating
> the power switch :-).
>
> >Maybe I'll try and get an automated build against the
> bleedperl going with my
> >"farm". What would be a good frequency to run such a thing?
> How often are
> >there new bleedperls, typically?
>
> It depends on what you mean by a "new bleadperl". Every patch that's
> applied gets a number assigned and the Perl at the latest patchlevel
> is bleadperl. The canonical method for building bleadperl is to use
> rsynch to extract the latest source from the repository, but I don't
> think there is an rsynch for VMS. This is all described better and
> more authoritatively in
>
> $ perdock perlhack
>
> or
>
> <http://www.perldoc.com/perl5.8.0/pod/perlhack.html>
>
> The downloadable snapshots are supplied by the pumpking at varying
> intervals; at the moment it's about every two weeks I think, but will
> get more frequent when there is a release pending. You can see what
> snapshots are available by looking at:
>
> <http://www.funet.fi/pub/languages/perl/snap/>
I guess that's more what I'd be interested in... I wouldn't want to
build every after every patch.
>
> The automated smoke reports are generated by a special extension
> created for that purpose:
>
> <http://search.cpan.org/author/ABELTJE/Test-Smoke-1.15/>
>
> It would be really nice to get that extension ported to VMS so we
> would simply show up in the reports. Getting Test::Smoke ported
> might require divorcing it from rsynch and making it work with
> snapshots, but I don't remember for sure.
> --
> ________________________________________
> Craig A. Berry
> mailto:[EMAIL PROTECTED]
>
> "... getting out of a sonnet is much more
> difficult than getting in."
> Brad Leithauser
>
