Front page | perl.perl5.porters |
Postings from January 2013
On Thu, Jan 03, 2013 at 02:30:40PM -0800, zengargoyle wrote: > Just fired up a first run try (mostly accepting defaults) on a > SunOS myhostname 5.9 Generic_122300-02 sun4u sparc SUNW,Ultra-5_10 > > Will see how long that takes to run a suite before maybe moving it to > one of our beefier but > actually used for something machines reniced. Might have to skip a > few of the tests, the > systems/security folks tend to frown on the wild ypcat everything test at least. > > Is there any further minimalization of the number of build > combinations that's still useful > without going full bore like the test on my Linux laptop building 16 > combinations over 10 hours? > Or maybe running only one of TEST vs harness or using parallel testing? > > Or any other tips for a smoketesting newb? Running with harness_only and enabling parallel testing will shorten the smoke testing time considerably, but increase system load. With respect to the configurations tested, the more configurations the better, especially Solaris specific configurations like -Dusedtrace and -Duse64bitall (which enables a 64-bit memory model), but even testing with just the basic -Duseithreads and -DDEBUGGING combinations is valuable. TonyThread Previous | Thread Next