develooper Front page | perl.perl5.porters | Postings from March 2014

Re: Inconsistent cpan/Win32API-File/t/file.t failure (was Re: Smoke[smoke-me/nicholas/openn] v5.19.9-200-g22d0f40 FAIL(F) MSWin32 Win2000 SP4(x86/1 cpu) {smoke-me})

From:
George Greer
Date:
March 19, 2014 23:34
Subject:
Re: Inconsistent cpan/Win32API-File/t/file.t failure (was Re: Smoke[smoke-me/nicholas/openn] v5.19.9-200-g22d0f40 FAIL(F) MSWin32 Win2000 SP4(x86/1 cpu) {smoke-me})
Message ID:
alpine.LFD.2.11.1403191923070.28023@ein.m-l.org
On Wed, 19 Mar 2014, Jan Dubois wrote:

> On Wed, Mar 19, 2014 at 3:42 AM, Nicholas Clark <nick@ccl4.org> wrote:
>>
>> That code is single-threaded in Perl, isn't it? So what might be holding
>> "open" the directory, but lets it go within 0.25s.
>
> I would look for any kind of filesystem monitoring services on the
> machine, like on-access virus scanners, or shell extensions (Dropbox,
> SkyDrive; don't know about version control plugins). All of them may
> keep handles to file and directory objects open and might need a
> little bit of idle time to recognize that the objects are gone and the
> handles should be closed.

Based on the test I'm guessing the blead smoker and smoke-me smoker were 
running that test at the same time and interfered with each other because 
the test uses a fixed name in the same directory.

It's a Windows 2000 VM set up specifically for Perl smoking so it doesn't 
have anything special like that.  Both drives are actual virtual drives 
under the full control of the VM, not shared folders, so there should not 
be any external interaction.  All the Perl stuff runs on D: to isolate it 
from the system drive.

I don't remember cpan/Win32API-File/t/file.t being one of the repeated 
intermittent failures.  (IPC-Cmd & threads.t#9)


-- 
George Greer



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