From: Shuah Khan <skhan@linuxfoundation.org>
To: Marco Elver <elver@google.com>, David Gow <davidgow@google.com>,
Brendan Higgins <brendanhiggins@google.com>
Cc: Arpitha Raghunandan <98.arpi@gmail.com>,
KUnit Development <kunit-dev@googlegroups.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] kunit: Fix result propagation for parameterised tests
Date: Fri, 11 Jun 2021 11:44:01 -0600 [thread overview]
Message-ID: <8a7e6806-97f5-6f13-5e97-328cf0d3a95d@linuxfoundation.org> (raw)
In-Reply-To: <CANpmjNOvLz=71PXSi+LGvKZ+9b_rfY1+wp8HfeyZa8u2QZURcg@mail.gmail.com>
On 6/11/21 2:29 AM, Marco Elver wrote:
> On Fri, 11 Jun 2021 at 05:57, David Gow <davidgow@google.com> wrote:
>>
>> When one parameter of a parameterised test failed, its failure would be
>> propagated to the overall test, but not to the suite result (unless it
>> was the last parameter).
>>
>> This is because test_case->success was being reset to the test->success
>> result after each parameter was used, so a failing test's result would
>> be overwritten by a non-failing result. The overall test result was
>> handled in a third variable, test_result, but this was disacarded after
>> the status line was printed.
>>
>> Instead, just propagate the result after each parameter run.
>>
>> Signed-off-by: David Gow <davidgow@google.com>
>> Fixes: fadb08e7c750 ("kunit: Support for Parameterized Testing")
>
> Reviewed-by: Marco Elver <elver@google.com>
>
> Would Cc: stable be appropriate?
>
> Thanks,
> -- Marco
>
>> ---
>>
>> This is fixing quite a serious bug where some test suites would appear
>> to succeed even if some of their component tests failed. It'd be nice to
>> get this into kunit-fixes ASAP.
>>
Will apply this with cc stable.
>> (This will require a rework of some of the skip tests work, for which
>> I'll send out a new version soon.)
>>
Thanks for the heads up. I will wait for new version.
thanks,
-- Shuah
next prev parent reply other threads:[~2021-06-11 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 3:57 [PATCH] kunit: Fix result propagation for parameterised tests David Gow
2021-06-11 8:29 ` Marco Elver
2021-06-11 17:44 ` Shuah Khan [this message]
2021-06-11 23:16 ` David Gow
2021-06-11 20:26 ` Brendan Higgins
2021-06-11 23:14 ` David Gow
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=8a7e6806-97f5-6f13-5e97-328cf0d3a95d@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=98.arpi@gmail.com \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=elver@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.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