On Wed, 22 Feb 2012, George Greer wrote: > Smoke logs available at http://m-l.org/~perl/smoke/perl/ > > Automated smoke report for 5.15.8 patch e2f198a1a89361c559b68be129d3e8ef66e8cd06 v5.15.8-15-ge2f198a > perl-win2k: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz(~38641 MHz) (x86/1 cpu) > on MSWin32 - Win2000 SP4 > using cl version 14.00.50727.762 > smoketime 5 hours 34 minutes (average 1 hour 23 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 > > v5.15.8-15-ge2f198a Configuration (common) none > ----------- --------------------------------------------------------- > F F > F F -Duseithreads > | +--------- -DDEBUGGING > +----------- no debugging > > > Locally applied patches: > uncommitted-changes > SMOKEe2f198a1a89361c559b68be129d3e8ef66e8cd06 > > Failures: (common-args) none > [default] > [default] -DDEBUGGING > ../cpan/Memoize/t/expmod_t.t................................FAILED > 11-12, 15 > ../cpan/Time-HiRes/t/usleep.t...............................FAILED > 3-6 > Non-zero exit status: 4 FYI, I switched the VM to SMP mode (with 1 CPU) which seems to have fixed the negative time problem but irritated Time::HiRes's usleep.t. If it avoids the build failures that happened due to the clock going backwards when in uniprocessor mode then maybe it'll be worth it or I can find a fix to that too. I'll have to see. -- George GreerThread Previous