At 10:05 PM -0700 6/14/02, Bohan, Larry wrote: >Scratch this report. I re-ran this build, just now, from scratch. >(freshly init'ed disk) and I did not see this failure repeated. > >a from-scratch build is what I did originally (same acct, same evirons) >so I'm not sure what would account for the HeisenBug quality of this failure.
The lib/ExtUtils/t tests really have to be run as a group. The first one sets up quite a few temporary files, the middle ones do the actual testing, and the last one cleans up. Any interruption at any step or any failed clean-up from a previous run could bollox up the whole batch. I have not been seeing the failure you originally noted when rerunning the entire test suite, so that might have been a result of running a test by itself without its brethren. You can run the whole set like this: $ set default [.t] $ perl test -"v" [-.lib.extutils.t]*.t though you'd need to make sure in this case that "perl" points to the just-built perl in your source tree. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
