Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 20 Jul 2005 11:04:19 -0700 From: Michael G Schwern To: Scott Bolte Cc: "Gerrit P. Haase" , Andrew Ho , cygwin AT cygwin DOT com, makemaker AT perl DOT org, perl5-porters AT perl DOT org, petdance AT cpan DOT org Subject: Re: [perl-5.8.7] Perl regression tests fail when lib directory is present Message-ID: <20050720180419.GA16999@windhund.schwern.org> References: <200507200216 DOT j6K2G3IL011560 AT crag DOT niss DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200507200216.j6K2G3IL011560@crag.niss.com> User-Agent: Mutt/1.4.2.1i On Tue, Jul 19, 2005 at 09:16:03PM -0500, Scott Bolte wrote: > It is not a perl bug. It is something in the TH module. > > I tested with perl 5.8.7 and the previous 5.8.6. I also, > through -I, tried both the old and new modules. It clearly > is the new Test::Harness module. It could be that something a new TH is doing triggers a perl bug. I really don't see how its otherwise. > Here is the test matrix. > > Modules > 5.8.6 5.8.7 > ----- ----- > Perl 5.8.6: worked failed > 5.8.7: worked failed > > The Test::Harness.pm version packaged by cygwin went from > 2.42 to 2.52. > > I'll try to carve out some time tomorrow or the next > day to dig in further. I would suggest working backwards though the CPAN versions of Test::Harness until it works. Then we can better spot the change which caused this bug. http://search.cpan.org/dist/Test-Harness/ -- Michael G Schwern schwern AT pobox DOT com http://www.pobox.com/~schwern Don't try the paranormal until you know what's normal. -- "Lords and Ladies" by Terry Prachett -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/