On Wed, 02 Apr 2008 11:21:23 +0200, Bram <[EMAIL PROTECTED]> wrote: > >> And are there any guides on how to start smoking? > > > > None besides the link below. > > > >> All I can find is a reference in perlhack which links to > >> http://search.cpan.org/dist/Test-Smoke/lib/Test/Smoke/FAQ > > > > If you tell us where that document, along with > > http://search.cpan.org/~abeltje/Test-Smoke/README > > come short in explaining what to do to start, we can improve that. > > Ok. > > I was already planning on starting to play with it and keeping a list of > things I do and problems/confusions I see. > (And then use that to suggest how to make the process more smoothly and/or > turn that into a mini doc) > > > If your system has reliable locales, esp UTF-8 locales are the > > interesting ones, you can add 30% testing time by telling smoke > > to test that too. > > What exactly qualifies as reliable localces?
The one's you use in daily life? I'm using Unicode a lot, and most of my xterm's live in some variant of en_US.UTF-8 or univ.utf8 Some systems pretend that they have implemented locales, but once they face the real use, they fail. Linux is know for pretty good locale implementations (at least compared to AIX in my perception) > >> Also, how long does a smoke - on average - take? (I suppose this depends > >> on the config?) > > > > Yes, and on the machine speed. (CPU(s), Memory, availability). I myself > > also smoke for two different compilers: the system native compiler and > > GNU gcc. If gcc is your default compiler (linux), you might consider > > smoking with g++ too. > > Would it be useful/intresting to test different versions of gcc aswell? yes. especially if you have bleeding edge gcc (as in not yet officially released), so new messages pop out fast before the mass gets hurt. Also gcc-3 versus gcc-4 is good to see > The systems I can use: > > linux 2.4.18: > - 24/24, 7/7: i686: Intel(R) Celeron(R) CPU 1.70GHz (Debian Woody) x 2 > > linux 2.4.25: > - 24/24, 7/7: i686: Intel(R) Celeron(R) CPU 2.40GHz (Debian Woody) > > linux 2.4.33: > - 5 hours: i686: Intel(R) Celeron(TM) CPU 1300MHz (Slackware) > > linux 2.6.22: > - 5 hours: i686: Intel(R) Pentium(R) Dual CPU E2160 @ 1.80GHz (2 core - > Debian etch) > > linux: 2.6.9-42: > - 5 hours: i686: 2 x Dual Core AMD Opteron(tm) Processor 265 1800 1.70GHz > (4 core - CentOS) for similar architectures, you might consider different smokes. Say to smoke 5.8.x on machine A, 5.10.x on machine B and 5.11.x on machine C Looking forward to see your results -- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using & porting perl 5.6.2, 5.8.x, 5.10.x on HP-UX 10.20, 11.00, 11.11, & 11.23, SuSE 10.1 & 10.2, AIX 5.2, and Cygwin. http://qa.perl.org http://mirrors.develooper.com/hpux/ http://www.test-smoke.org http://www.goldmark.org/jeff/stupid-disclaimers/
