Hi,
On Tue, Sep 19, 2023 at 03:48:55PM -0400, Rae Moar wrote:
> On Mon, Sep 11, 2023 at 5:51 AM Maxime Ripard <mripard@xxxxxxxxxx> wrote:
> >
> > Kunit recently gained support to setup attributes, the first one being
> > the speed of a given test, then allowing to filter out slow tests.
> >
> > A slow test is defined in the documentation as taking more than one
> > second. There's an another speed attribute called "super slow" but whose
> > definition is less clear.
> >
> > Add support to the test runner to check the test execution time, and
> > report tests that should be marked as slow but aren't.
> >
> > Signed-off-by: Maxime Ripard <mripard@xxxxxxxxxx>
>
> I like this idea especially if it was helpful in identifying slow
> tests already! I have a few thoughts on this. I share Jani's concern
> for warning all tests on slow machines. I can think of a few options.
>
> First, we could increase the threshold to about 2s even though that
> would eliminate warnings on potentially slow tests. However, this
> would point out the slowest tests.
I don't have a strong opinion there, so whatever works for you :)
> Second, we could change this to warn users only when they choose by
> making this a configurable option or making this a script to output a
> list of all unmarked slow tests.
I'm not really sure. Adding an option would hide it away from users and
only a fraction of the users (including devs working on tests) would see
that their test should actually be marked as slow.
That will prevent the wider use of it imo, and instead of catching it
early (when we're working on it), will lead to more patches.
Plus, a runtime of more than a second, no matter the platform, is
usually a good indication that what your test is doing probably
shouldn't be done that way.
> Third, we could leave this as is. As the KUnit warnings do not show up
> in the kunit.py output and do not cause the test to fail in any way
> they are relatively harmless if they are unwanted by the user.
I was looking at it the other day, and I think we can modify the TAP
output to expose the warning through the kunit.py command to the user.
It looks like it allows to provide any keyword after the comment mark
and allows to extend it, so we could have something like
ok $TEST # KUNIT_WARN $MESSAGE
and then parse that in kunit.py, pretty much like we handle SKIP. But
that's a separate discussion really.
But yeah, whether or not this is reported to the user, it must not fail
the test.
> Not quite sure which I prefer? The second option might be the cleanest
> for the user and the time threshold could even be customizable. Let me
> know what you think.
I'm in favour of the second one as well.
> > ---
> > lib/kunit/test.c | 16 ++++++++++++++++
> > 1 file changed, 16 insertions(+)
> >
> > diff --git a/lib/kunit/test.c b/lib/kunit/test.c
> > index 49698a168437..a3b924501f3d 100644
> > --- a/lib/kunit/test.c
> > +++ b/lib/kunit/test.c
> > @@ -379,6 +379,9 @@ static void kunit_run_case_internal(struct kunit *test,
> > struct kunit_suite *suite,
> > struct kunit_case *test_case)
> > {
> > + struct timespec64 start, end;
> > + struct timespec64 duration;
> > +
> > if (suite->init) {
> > int ret;
> >
> > @@ -390,7 +393,20 @@ static void kunit_run_case_internal(struct kunit *test,
> > }
> > }
> >
> > + ktime_get_ts64(&start);
> > +
> > test_case->run_case(test);
> > +
> > + ktime_get_ts64(&end);
> > +
> > + duration = timespec64_sub(end, start);
> > +
> > + if (duration.tv_sec >= 1 &&
> > + (test_case->attr.speed == KUNIT_SPEED_UNSET ||
> > + test_case->attr.speed >= KUNIT_SPEED_NORMAL))
> > + kunit_warn(test,
> > + "Test should be marked slow (runtime: %lld.%09lds)",
> > + duration.tv_sec, duration.tv_nsec);
>
> I would consider moving this if statement into a separate function.
Ack.
I'll send a v2 with your suggestions
Thanks!
Maxime
Attachment:
signature.asc
Description: PGP signature
