develooper Front page | perl.perl5.porters | Postings from December 2008

Re: Smoke [5.11.0] 35106 FAIL(F) MSWin32 WinXP/.Net SP3 (x86/2 cpu)

Thread Previous | Thread Next
From:
Jos I. Boumans
Date:
December 16, 2008 08:24
Subject:
Re: Smoke [5.11.0] 35106 FAIL(F) MSWin32 WinXP/.Net SP3 (x86/2 cpu)
Message ID:
77C67268-8360-4420-8ED1-3F52BB9674FA@dwim.org
Hi Steve,

On Dec 16, 2008, at 12:26 PM, Steve Hay wrote:

> Jos I. Boumans wrote:
>> On Dec 16, 2008, at 7:26 AM, Steve Hay wrote:
>>>
>>> [default] -DDEBUGGING -Duseithreads -Duselargefiles
>>> ../ext/PerlIO/t/ioleaks.t...................................FAILED
>>> ../lib/Archive/Extract/t/01_Archive-Extract.t...............FAILED
>>>     126, 128-129, 131-133, 190, 192-193, 195-197
>>
>> This is with your fix to A::E already isn't it? Any clue what's
>> causing tis failure? Might it be related to the PerlIO failure?
>>
>
> Yes, that's with my fix. The failures are not related to the PerlIO
> "failure" (which is actually a passed TODO, which Test::Smoke wrongly
> shows as a FAIL whenever anything else fails), but are actually caused
> by my smoke environment having a Cygwin bin/ folder in its PATH (used
> for the rsync). The Archive::Extract tests therefore picked up some
> binaries (tar, gzip, etc.) that weren't available in my PATH when I  
> was
> testing manually, and it seems that these Cygwin binaries don't work
> nicely in a DOS window.

Thanks for looking into this. This is a very unfortunate 'make test'
failure, as it's a common set up for Win32 users to have cygwin in
their path.

Unfortunately, i dont see a reliable way to detect this, let alone
'fix it' so users aren't affected by this... 'feature'.

If you have any suggestions, I'm happy to take them onboard, but I
guess for now we'll just leave this as an acceptable failure and move
on.

What do you think?

> Specifically, the first failing test is a failure to extract the y.tar
> test file. The command being run is something like
>
> C:\cygwin\bin\tar.EXE -xf
> C:\p5p\BLEADP~1\lib\Archive\Extract\t\src\y.tar
>
> which causes an error from the Cygwin binary:
>
> C: Unknown Host
> /usr/bin/tar: C\:\\p5p\\BLEADP~1\\lib\\Archive\\Extract\\t\\src\ 
> \y.tar:
> Cannot open: Input/Output error
> /usr/bin/tar: Error is not recoverable: exiting now
>
> I tried various other combinations (forward slashes instead of
> backslashes, "long pathnames" instead of "short pathnames" (i.e.
> "bleadperl" instead of "BLEADP~1"), but nothing works other than the
> insane /cygdrive nonsense:
>
> C:\cygwin\bin\tar.EXE -xf
> /cygdrive/C/p5p/bleadperl/lib/Archive/Extract/t/src/y.tar
>
> or a relative path:
>
> C:\cygwin\bin\tar.EXE -xf ../src/y.tar
>
> I think I'm just going to duck the issue by removing the Cygwin bin/
> folder from my PATH after the rsync has completed!


--
	Jos Boumans
	
	"Never ask a man what computer he uses. If it's a Mac, he'll
	tell you. If it's not, why embarrass him?" - Tom Clancy
		


Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About