From: Liu Yiding <yidingx.liu@intel.com>
To: David Gow <davidgow@google.com>
Cc: KUnit Development <kunit-dev@googlegroups.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
"Li, Philip" <philip.li@intel.com>
Subject: Re: Kunit get 0 tests when run defconfig in Debian9
Date: Wed, 27 May 2020 09:59:03 +0800 [thread overview]
Message-ID: <41db8bbd-3ba0-8bde-7352-083bf4b947ff@intel.com> (raw)
In-Reply-To: <CABVgOSnj6H5UXNGktT2NAHPF1KxAu5=Mg0hyuBu+NpjAdh+Q4A@mail.gmail.com>
Hi, David.
Sorry for the delay and really appericated for your help !!!
On 5/22/20 10:33 AM, David Gow wrote:
> A few questions/suggestions:
> - Are there any test results visible when running
> ./tools/testing/kunit/kunit.py run --raw_output (older versions of
> the KUnit parser may not work well if the kernel log is decorated,
> e.g. with timestamps, etc — this should be largely fixed for 5.7).
--raw_output is really helpful.
The root cause of missing tests is that tempdir doesn't exist.
I create that file and kunit runs well now. :-P
```
root@vm-snb-195 ~/linus# ./tools/testing/kunit/kunit.py run --raw_output
--defconfig
Generating .config ...
[09:35:37] Building KUnit Kernel ...
arch/um/os-Linux/signal.c: In function ‘sig_handler_common’:
arch/um/os-Linux/signal.c:51:1: warning: the frame size of 2960 bytes is
larger than 2048 bytes [-Wframe-larger-than=]
}
^
arch/um/os-Linux/signal.c: In function ‘timer_real_alarm_handler’:
arch/um/os-Linux/signal.c:95:1: warning: the frame size of 2960 bytes is
larger than 2048 bytes [-Wframe-larger-than=]
}
^
[09:39:48] Starting KUnit Kernel ...
Core dump limits :
soft - 0
hard - 0
Checking that ptrace can change system call numbers...OK
Checking syscall emulation patch for ptrace...OK
Checking advanced syscall emulation patch for ptrace...OK
Checking environment variables for a tempdir.../lkp/lkp/src/tmp
Checking if /lkp/lkp/src/tmp is on tmpfs...No such file or directory
Warning: tempdir /lkp/lkp/src/tmp is not on tmpfs
[09:39:48] Elapsed time: 257.808s total, 6.515s configuring, 251.274s
building, 0.018s running
```
--
Best regards.
Liu Yiding
prev parent reply other threads:[~2020-05-27 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 5:56 Kunit get 0 tests when run defconfig in Debian9 kernel test robot
2020-05-22 2:33 ` David Gow
2020-05-22 11:42 ` Alan Maguire
2020-05-27 1:59 ` Liu Yiding [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=41db8bbd-3ba0-8bde-7352-083bf4b947ff@intel.com \
--to=yidingx.liu@intel.com \
--cc=davidgow@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=philip.li@intel.com \
/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).