From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: brendanhiggins@google.com, skhan@linuxfoundation.org
Cc: kunit-dev@googlegroups.com, linux-kselftest@vger.kernel.org
Subject: Re: kunit stopped working
Date: Mon, 21 Dec 2020 16:45:10 +0200 [thread overview]
Message-ID: <20201221144510.GS4077@smile.fi.intel.com> (raw)
In-Reply-To: <20201221144302.GR4077@smile.fi.intel.com>
On Mon, Dec 21, 2020 at 04:43:02PM +0200, Andy Shevchenko wrote:
> Hi!
>
> For last few weeks KUnit stopped working. Any insight?
>
> P.S. I guess no need to tell that my kernel on which I run tests has not been
> changed as well as command line for wrapper:
>
> tools/testing/kunit/kunit.py run --build_dir ~/$OUT_DIR
Current output (expected 18 tests to be run from several modules):
$ tools/testing/kunit/kunit.py run --build_dir ~/$OUT_DIR
[16:42:24] Configuring KUnit Kernel ...
[16:42:24] Building KUnit Kernel ...
[16:42:28] Starting KUnit Kernel ...
[ERROR] no tests run!
[16:42:28] ============================================================
[16:42:28] Testing complete. 0 tests run. 0 failed. 0 crashed.
[16:42:28] Elapsed time: 3.563s total, 0.002s configuring, 3.441s building, 0.000s running
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-12-21 14:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 14:43 kunit stopped working Andy Shevchenko
2020-12-21 14:45 ` Andy Shevchenko [this message]
2020-12-21 18:37 ` Shuah Khan
2020-12-21 19:27 ` Andy Shevchenko
2020-12-21 19:40 ` Andy Shevchenko
2020-12-21 20:03 ` Andy Shevchenko
2020-12-22 1:43 ` David Gow
2020-12-22 7:26 ` David Gow
2020-12-22 13:34 ` Andy Shevchenko
2020-12-27 19:58 ` Brendan Higgins
2021-01-05 16:17 ` Petr Mladek
2021-01-05 16:49 ` Petr Mladek
2021-01-06 4:04 ` Sergey Senozhatsky
2021-01-06 13:10 ` Petr Mladek
2021-01-07 7:15 ` Sergey Senozhatsky
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=20201221144510.GS4077@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brendanhiggins@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=skhan@linuxfoundation.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