Front page | perl.perl5.porters |
Postings from March 2014
Re: [perl #121230] process group kill on Win32 broken in5.17.2,regression 5.18
Thread Previous
|
Thread Next
From:
Steve Hay
Date:
March 24, 2014 23:09
Subject:
Re: [perl #121230] process group kill on Win32 broken in5.17.2,regression 5.18
Message ID:
CADED=K7MNvZQ3VF76TVkx4HBwSWZBJRLuxOe6nRjXjkk8d1U-g@mail.gmail.com
On 24 March 2014 21:58, bulk88 <bulk88@hotmail.com> wrote:
> Dave Mitchell wrote:
>>
>> On Mon, Mar 24, 2014 at 07:19:37AM -0700, Ricardo SIGNES via RT wrote:
>>>
>>> bulk88 requested that this be marked a 5.20.0 blocker, but I'm not
>>> entirely sure what issue remains on the ticket, on which discussion has sort
>>> of meandered.
>>>
>>> (a) is this still a blocker candidate?
>>> (b) what's up?
>>
>>
>> The bug has been fixed, but the just-added test is failing on George's
>> smoker, but not for bulk88.
>>
>> So we either need to get the test fixed, or backout the new test.
>>
>
> 5.18 maint backport is also a possibility since this is a regression for a
> feature nobody knew existed, except for probably demerphq (who wrote IIRC)
> and he doesnt use Windows anymore. But first figuring out why the George
> smoker failed is required. Steve Hay, Tony, can you 2 trying building Win32
> Perl and see what happens? There arent any active Win32 porters other than
> me, Hay and Cook AFAIK.
Sorry, I had assumed that I couldn't reproduce either this since my
recent perl build/tests have all been happily passing, but on closer
inspection I see that George's smoker only fails without useithreads.
So I built with USE_MULTI=undef USE_ITHREADS=undef USE_IMP_SYS=undef
and sure enough it fails:
C:\Dev\Git\perl\t>..\perl harness -v op\kill0.t
op/kill0.t ..
1..9
ok 1 - kill(0, $pid) returns true if $pid exists
ok 2 - kill(0, $pid) returns false if $pid does not exist
ok 3 - dies killing undef pid
ok 4 - dies killing empty string pid
ok 5 - dies killing alphabetic pid
ok 6 - can kill a number string in a magic variable
# Failed test 7 - process group kill, named signal at op/kill0.t line 82
# got "0"
# expected "1"
not ok 7 - process group kill, named signal
ok 8 - $Config{sig_name} parsed correctly
# Failed test 9 - process group kill, numeric signal at op/kill0.t line 107
# got "0"
# expected "1"
not ok 9 - process group kill, numeric signal
Failed 2/9 subtests
Test Summary Report
-------------------
op/kill0.t (Wstat: 0 Tests: 9 Failed: 2)
Failed tests: 7, 9
Files=1, Tests=9, 2 wallclock secs ( 0.05 usr + 0.00 sys = 0.05 CPU)
Result: FAIL
I don't have time to look right now, but will dig deeper tomorrow...
Thread Previous
|
Thread Next