zsh-workers
 help / color / mirror / code / Atom feed
From: Chris Down <chris@chrisdown.name>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH v2 2/2] builtins: kill: Do not signal current process group when pid is empty
Date: Mon, 17 Feb 2020 09:11:44 -0500	[thread overview]
Message-ID: <20200217141144.GB20166@chrisdown.name> (raw)
In-Reply-To: <20200216103954.GC15773@tarpaulin.shahaf.local2>

Daniel Shahaf writes:
>Chris Down wrote on Sat, Feb 15, 2020 at 20:21:09 -0400:
>> 1. Add special handling to `kill` to avoid this case. See this patch[0]
>>    for a version that does that.
>
>> 0: https://www.zsh.org/mla/workers/2020/msg00251.html
>
>Suggest to state "workers/45426" next to the link: that's how we customarily
>refer to mailing lists posts.  The number comes from the X-Seq header and is
>shown in the archives too.

Sure thing. :-)

>> +++ b/Test/B11kill.ztst
>> @@ -50,3 +50,15 @@
>>    kill -INT
>>  1:kill with sigspec only
>>  ?(eval):kill:1: not enough arguments
>> +
>> +# Regression tests: `kill ''` should not result in `kill 0`.
>> +
>> +  trap 'exit 19' TERM
>> +  kill ''
>> +1:Plain kill with empty pid should not send signal to current process group
>> +?(eval):kill:2: illegal pid:
>
>Should this test use a subshell so as not to kill the test suite process in
>case the bug regresses?
>
>Personally, I'm partial to first adding commits in "expected to fail" mode
>(using the «f» flag after the expected exit code) and then in a separate commit
>fix the bug, since doing so in effect validates the test.  However, I see this
>as a nice-to-hvae, not a blocker.

For this particular one, the subshell won't help, since we're part of the same 
process group as make and the test runner regardless:

     make: *** [Makefile:263: check] User defined signal 1
     make[1]: *** [Makefile:190: check] User defined signal 1
     make[1]: Leaving directory '/home/cdown/git/zsh/Test'

One possibility to avoid that is to run these few tests in a shell that's a new 
session leader, like in W02jobs, I suppose. What do you think about that?
>
>> +  trap 'exit 11' INT
>> +  kill -INT ''
>> +1:kill with empty pid and sigspec should not send signal to current process group
>> +?(eval):kill:2: illegal pid:
>
>Could you add a comment explaining the magic numbers 11 and 19?

Sure thing, will do in v3.

Thanks!

Chris

  reply	other threads:[~2020-02-17 14:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-16  0:20 [PATCH v2 1/2] builtins: kill: Add basic test suite Chris Down
2020-02-16  0:21 ` [PATCH v2 2/2] builtins: kill: Do not signal current process group when pid is empty Chris Down
2020-02-16 10:39   ` Daniel Shahaf
2020-02-17 14:11     ` Chris Down [this message]
2020-02-17 14:33       ` Daniel Shahaf
2020-02-16 10:34 ` [PATCH v2 1/2] builtins: kill: Add basic test suite Daniel Shahaf
2020-02-17 13:49   ` Chris Down

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200217141144.GB20166@chrisdown.name \
    --to=chris@chrisdown.name \
    --cc=d.s@daniel.shahaf.name \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).