Re: Solaris ubersmoke now operational
[email protected] (Abe Timmerman) Fri, 8 Aug 2003 17:56:00 +0200
| Newsgroups | perl.daily-build |
|---|---|
| Organization | ztreet |
| Message-ID | <[email protected]> |
Op een zonnige zomerdag (Friday 08 August 2003 17:18), schreef Alan Burlison:
> Abe Timmerman wrote:
<snip>
> > It's on its way, I'm doing the last tests right now and it will be on
> > CPAN as 1.18.02 shortly (pant, pant...)
Due to a power failure in the office-building, my repository server is
offline, so it could be monday before I can do a new release :(
> I'll also hack up something to get the progress of a test. Is there any
> easy way of figuring out how many test cycles are going to be run? Could
> something be printed to the logfile? S simple grep of the logfile would
> then be enough to figure out what was going on.
To get the configurations already processed (including the one in process)
something like:
$ grep ^Configuration <builddir>/mktest.out
For more F<mktest.out> parsing stuff (including timestamps) see F<mkovz.pl>
To get all the configurations to be processed, something like:
#! /usr/bin/perl -w
use strict;
use Test::Smoke::BuildCFG;
use Test::Smoke;
my $bldcfg = shift or die "Usage: $0 <buildconfig>\n";
my $bcf = Test::Smoke::BuildCFG->new( $bldcfg );
foreach my $config ( $bcf->configurations ) {
print "$config\n" unless Test::Smoke::skip_config( $config );
}
__END__
Good luck,
Abe
--
Rafael> Actually you're thinking aloud, here ?
Yes?
No?
Maybe?
-- Jarkko Hietaniemi on p5p @ 2003-02-17