From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Shuah Khan <skhan@linuxfoundation.org>, Petr Mladek <pmladek@suse.com>
Cc: brendanhiggins@google.com, kunit-dev@googlegroups.com,
linux-kselftest@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: kunit stopped working
Date: Mon, 21 Dec 2020 21:40:08 +0200 [thread overview]
Message-ID: <20201221194008.GA4077@smile.fi.intel.com> (raw)
In-Reply-To: <20201221192757.GZ4077@smile.fi.intel.com>
+Cc people from culprit commit
On Mon, Dec 21, 2020 at 09:27:57PM +0200, Andy Shevchenko wrote:
> On Mon, Dec 21, 2020 at 11:37:44AM -0700, Shuah Khan wrote:
> > On 12/21/20 7:45 AM, Andy Shevchenko wrote:
> > > 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
>
> > Please give more details on which repo you are using and the what's
> > the top commit.
>
> v5.10 - OK
>
> [21:24:14] Testing complete. 14 tests run. 0 failed. 0 crashed.
>
> Linux Next 20201221 - Not OK.
>
> I'm expecting that v5.11-rc1 will be broken.
Luckily it's easy to bisect:
# bad: [3b45c156c48f6fa078789df83c3174f96d01ecb8] defconfig: remove everything that is not needed for netboot
# good: [2c85ebc57b3e1817b6ce1a6b703928e113a90442] Linux 5.10
# good: [2cffa11e2aa76a0560c890f057858b68fe744d03] Merge tag 'irq-core-2020-12-15' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
# bad: [9805529ec544ea7a82d891d5239a8ebd3dbb2a3e] Merge tag 'arm-soc-dt-5.11' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
# bad: [ac7ac4618cf25e0d5cd8eba83d5f600084b65b9a] Merge tag 'for-5.11/block-2020-12-14' of git://git.kernel.dk/linux-block
# good: [8958b2491104d7f254cff0698505392582dbc13a] mm: fix some spelling mistakes in comments
# good: [6febd8bef36e64fc1f4aaff1f6302be5c653ad64] Merge branch 'signal-for-v5.11' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace
# bad: [8312f41f08edc641aa927d31fb71319694ae9c42] Merge tag 'mips_5.11' of git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux
# bad: [ca5b877b6ccc7b989614f3f541e9a1fe2ff7f75a] Merge tag 'selinux-pr-20201214' of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux
# good: [157807123c94acc8dcddd08a2335bd0173c5d68d] Merge tag 'asm-generic-mmu-context-5.11' of git://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic
# good: [7194850efa47c8dac6e805087dd23c7b03af019d] Merge tag 'linux-kselftest-next-5.11-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
# bad: [d3eb52113d162cc88975fbd03c9e6f9cf2f8a771] Merge tag 'printk-for-5.11' of git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux
# good: [5e60366d56c630e32befce7ef05c569e04391ca3] Merge tag 'fallthrough-fixes-clang-5.11-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux
# bad: [5f3b8d398601055f29f32986a94d55955cd48f09] Merge branch 'for-5.11-null-console' into for-linus
# bad: [3cffa06aeef7ece30f6b5ac0ea51f264e8fea4d0] printk/console: Allow to disable console output by using console="" or console=null
# bad: [757055ae8dedf5333af17b3b5b4b70ba9bc9da4e] init/console: Use ttynull as a fallback when there is no console
# first bad commit: [757055ae8dedf5333af17b3b5b4b70ba9bc9da4e] init/console: Use ttynull as a fallback when there is no console
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-12-21 19:40 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
2020-12-21 18:37 ` Shuah Khan
2020-12-21 19:27 ` Andy Shevchenko
2020-12-21 19:40 ` Andy Shevchenko [this message]
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=20201221194008.GA4077@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brendanhiggins@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=pmladek@suse.com \
--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