From: Kees Cook <keescook@chromium.org>
To: shuah <shuah@kernel.org>
Cc: Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] selftests/harness: Handle timeouts cleanly
Date: Fri, 13 Mar 2020 16:10:18 -0700 [thread overview]
Message-ID: <202003131609.228C4BBEDE@keescook> (raw)
In-Reply-To: <5da3bc61-6e43-f6d4-9623-0f4f1cb8e76a@kernel.org>
On Fri, Mar 13, 2020 at 11:25:58AM -0600, shuah wrote:
> Hi Kees,
>
> On 3/11/20 3:17 PM, Kees Cook wrote:
> > When a selftest would timeout before, the program would just fall over
> > and no accounting of failures would be reported (i.e. it would result in
> > an incomplete TAP report). Instead, add an explicit SIGALRM handler to
> > cleanly catch and report the timeout.
> >
> > Before:
> >
> > [==========] Running 2 tests from 2 test cases.
> > [ RUN ] timeout.finish
> > [ OK ] timeout.finish
> > [ RUN ] timeout.too_long
> > Alarm clock
> >
> > After:
> >
> > [==========] Running 2 tests from 2 test cases.
> > [ RUN ] timeout.finish
> > [ OK ] timeout.finish
> > [ RUN ] timeout.too_long
> > timeout.too_long: Test terminated by timeout
> > [ FAIL ] timeout.too_long
> > [==========] 1 / 2 tests passed.
> > [ FAILED ]
> >
>
> This is good info. to capturein the commit logs for the patches.
The cover letter is an exact copy of patch 2's commit log. :)
> Please add them and send v2. You can also fix the subject prefix
> at the same time :)
I'll resend a v2 with fixed prefix regardless.
--
Kees Cook
prev parent reply other threads:[~2020-03-13 23:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 21:17 [PATCH 0/2] selftests/harness: Handle timeouts cleanly Kees Cook
2020-03-11 21:17 ` [PATCH 1/2] selftests/seccomp: Move test child waiting logic Kees Cook
2020-03-12 4:52 ` Kees Cook
2020-03-11 21:17 ` [PATCH 2/2] selftests/harness: Handle timeouts cleanly Kees Cook
2020-03-13 17:25 ` [PATCH 0/2] " shuah
2020-03-13 23:10 ` Kees Cook [this message]
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=202003131609.228C4BBEDE@keescook \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=shuah@kernel.org \
--cc=wad@chromium.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.
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).