Bug #96998 for Proc-Pidfile: pidfile.t hangs on Windows

Sun Jul 06 13:47:26 2014 CHORNY [...] cpan.org - Ticket created

Subject:

pidfile.t hangs on Windows

1..24 ok 1 - require Proc::Pidfile; ok 2 - pidfile created ok 3 - pidfile destroyed ok 4 - temp pidfile matches ok 5 - temp pidfile created ok 6 - temp pidfile destroyed ok 7 - open pidfile ok 8 - close pidfile ok 9 - pid correct ok 10 - fork successful (in cleanup) The getppid function is unimplemented at C:\strawberry160\cpan\build\Proc-Pidfile-1.05-7cIq7A\blib\lib/Proc/Pidfile.pm line 139. ok 11 - child exited ok 12 - child ignored parent's pidfile ok 13 - child ignored pidfile ok 14 - parent destroyed pidfile ok 15 - fork successful t/pidfile.t already running: 832 (C:\DOCUME~1\a\LOCALS~1\Temp/pidfile.t.pid) at t/pidfile.t line 67. (in cleanup) The getppid function is unimplemented at C:\strawberry160\cpan\build\Proc-Pidfile-1.05-7cIq7A\blib\lib/Proc/Pidfile.pm line 139. ok 16 - child exited ok 17 - child spotted existing pidfile ok 18 - fork successful (in cleanup) The getppid function is unimplemented at C:\strawberry160\cpan\build\Proc-Pidfile-1.05-7cIq7A\blib\lib/Proc/Pidfile.pm line 139. ok 19 - silent child exited ok 20 - child spotted and ignored existing pidfile ok 21 - open pidfile ok 22 - bogus pidfile ignored ok 23 - open pidfile (hangs) -- Alexandr Ciornii, http://chorny.net

Mon Jul 07 19:35:42 2014 NEILB [...] cpan.org - Correspondence added

Show quoted text

> (hangs)

Thanks for the report. I've released 1.06, which should stop the hang. I still need to work a bit more at the right behaviour on Windows! Cheers, Neil

Mon Jul 07 19:35:43 2014 The RT System itself - Status changed from 'new' to 'open'

Mon Jul 07 19:35:44 2014 NEILB [...] cpan.org - Taken

Mon Jul 07 22:38:35 2014 CHORNY [...] cpan.org - Correspondence added

On Mon Jul 07 19:35:42 2014, NEILB wrote: Show quoted text

> > (hangs)

> > Thanks for the report. I've released 1.06, which should stop the hang.

Still hangs 1..24 ok 1 - require Proc::Pidfile; ok 2 - pidfile created ok 3 - pidfile destroyed ok 4 - temp pidfile matches ok 5 - temp pidfile created ok 6 - temp pidfile destroyed ok 7 - open pidfile ok 8 - close pidfile ok 9 - pid correct ok 10 - fork successful ok 11 - child exited ok 12 - child ignored parent's pidfile ok 13 - child ignored pidfile ok 14 - parent destroyed pidfile ok 15 - fork successful t/pidfile.t already running: 456 (C:\DOCUME~1\a\LOCALS~1\Temp/pidfile.t.pid) at t/pidfile.t line 67. ok 16 - child exited ok 17 - child spotted existing pidfile ok 18 - fork successful ok 19 - silent child exited ok 20 - child spotted and ignored existing pidfile ok 21 - open pidfile ok 22 - bogus pidfile ignored ok 23 - open pidfile -- Alexandr Ciornii, http://chorny.net

Sun Sep 09 17:33:43 2018 NEILB [...] cpan.org - Correspondence added

Does the latest release -- 1.08 -- work for you?

Sat Jul 20 17:44:47 2019 NEILB [...] cpan.org - Correspondence added

No CPAN Testers failures for the latest release, so assuming this problem is now fixed.

Sat Jul 20 17:44:48 2019 NEILB [...] cpan.org - Status changed from 'open' to 'resolved'

Sat Jul 20 17:44:48 2019 NEILB [...] cpan.org - Fixed in 1.09 added