On Wed, 23 Apr 2014, bulk88 via RT wrote: > On Thu Apr 03 23:27:06 2014, bulk88 wrote: >> On Thu Mar 27 11:02:51 2014, bulk88 wrote: >>> On Thu Mar 27 06:01:15 2014, shay wrote: >>>> On 27 March 2014 07:41, bulk88 via RT <perlbug-followup@perl.org> >>>>> >>>>> kill0.t passed for me on no-threads perl with this patch. I >>>>> couldn't >>>>> make harness finish due to a different bug. >>>> >>>> Thanks, applied as 721b26746b. (A full "nmake test 2>nul" with no >>>> PERL_IMPLICIT_SYS passed all tests for me.) >>>> >>>> Does this complete #121230 now? I.e. should the ticket be closed >>>> now? >>> >>> Lets wait until the George smoker delivers a new report. I see >>> nothing >>> since Mar 23 on the Win2k smoker >>> http://www.nntp.perl.org/group/perl.daily-build.reports/ . >> >> Mar 23 is still the last smoke. I think it hung. Its been 12 days >> with no response. > > George the human responded about problems with the process group kill code in Message-ID: <alpine.LFD.2.11.1404222133090.31829@ein.m-l.org> . Its not showing up on nttp.perl.org yet so I can't offer a link. Archives of the logs and reports are always on my web site: http://m-l.org/~perl/smoke/perl/win32/blead/ Yes, the process group kill code is probably nuking the Win32 blead smoker. The maint and smoke-me smokers haven't been killed, so the impact is limited but still annoying. (Kind of like the test in blead that is hanging and I manually kill every so often.) As for the reports, I had a hard drive go bad in the RAID5 so I shut the machine off until the warranty replacement arrived. I updated the status pages[1] but didn't mail the list as it wasn't "interesting enough". 1: http://m-l.org/~perl/smoke/perl/win32/blead/status http://m-l.org/~perl/smoke/perl/linux/blead_g++_quick/status ...etc... -- George GreerThread Previous | Thread Next