From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 0/2] Small fixes for nstool
Date: Thu, 7 Nov 2024 15:54:43 +0100 [thread overview]
Message-ID: <20241107155443.599e7d35@elisabeth> (raw)
In-Reply-To: <20241106030322.2132051-1-david@gibson.dropbear.id.au>
On Wed, 6 Nov 2024 14:03:20 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> While working on the exeter tests, I noticed a couple of things
> missing in nstool. These make sense standalone, even if we don't have
> an urgent need for them without the exeter tests.
>
> David Gibson (2):
> test: Rename propagating signal handler
> test: Make nstool hold robust against interruptions to control clients
Applied.
Actually, one much-needed improvement for nstool in the current test
framework (at least for my usage) would be to make it terminate when
needed.
A while ago, 'killall -9 nstool' entered my shell history and now it's
right there with 'git rebase --continue':
$ sort ~/.bash_history | uniq -c | sort -nr | grep -A1 'killall -9 nstool'
192 killall -9 nstool
192 git rebase --continue
--
Stefano
next prev parent reply other threads:[~2024-11-07 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 3:03 [PATCH 0/2] Small fixes for nstool David Gibson
2024-11-06 3:03 ` [PATCH 1/2] test: Rename propagating signal handler David Gibson
2024-11-06 3:03 ` [PATCH 2/2] test: Make nstool hold robust against interruptions to control clients David Gibson
2024-11-07 14:54 ` Stefano Brivio [this message]
2024-11-07 23:30 ` [PATCH 0/2] Small fixes for nstool David Gibson
2024-11-08 0:05 ` Stefano Brivio
2024-11-08 2:32 ` David Gibson
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=20241107155443.599e7d35@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
/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://passt.top/passt
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 IMAP folder(s).