From: shuah <shuah@kernel.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: linux-kselftest@vger.kernel.org, shuah <shuah@kernel.org>
Subject: Re: kselftest build broken?
Date: Wed, 12 Jun 2019 10:44:28 -0600 [thread overview]
Message-ID: <1e2cc74d-a6c2-0a73-ede5-c72df28e96b2@kernel.org> (raw)
In-Reply-To: <CACT4Y+bfz2F-p4xODb_=rU0+F-FJCC66MJW7q9DXd0UHoUfgwg@mail.gmail.com>
> >> I've deleted the test that caused reboot for now and the
> run_kselftest.sh script finished running, but I can't understand the
> result. Is it all passed? Or something failed? What failed?
> The output is as follows:
>
> ... screens of output ...
> # make swap with zram device(s)
> [ 5335.215175] Adding 1020k swap on /dev/zram0. Priority:-2 extents:1
> across:1020k SSFS
> # done with /dev/zram0
> # zram making zram mkswap and swapon: OK
> # zram swapoff: OK
> # zram cleanup
> [ 5335.420825] zram0: detected capacity change from 1048576 to 0
> # zram02 : [PASS]
> ok 1 selftests: zram: zram.sh
> ~/kselftest#
>
Hi Dmitry,
This is the 6th email from you in a span of 3 hours! I am just going to
respond this last one. Please try to summarize your questions instead of
sending email storm, so it will be easier to parse and more productive
for both of us.
I am not sure what you are asking here. kselftest has bunch of tests,
and you have to look at individual test results to see if they passed
or failed. If you are looking for aggregate result, ksefltest doesn't
keep track of that.
>
> docs say:
>
> "The above commands by default run the tests and print full pass/fail report.
> Kselftest supports "summary" option to make it easier to understand the test
> results....
> $ make summary=1 kselftest
> "
>
If you want to build and run tests on the same test system use
the following commands, after building kernel and rebooting the newly
installed kernel:
make kselftest or make -C tools/testing/selftests run_tests
If you want to just build and install to default location run:
make -C tools/testing/selftests install
This installs under tools/testing/selftests/install and creates
run_kselftest.sh
You can specify INSTALL_PATH as follows:
export INSTALL_PATH=/tmp/kselftest;
make -C tools/testing/selftest/install
I am seeing an error
/bin/sh: 1: llvm-readelf: not found
make[1]: *** No rule to make target 'emit_tests'. Stop.
chmod u+x /tmp/kselftest/run_kselftest.sh
in both of the above. Something broke and I will look into it.
This doesn't break the install and run_kselftest.sh generation
About summary option:
make -C tools/testing/selftests/ summary=1 install
probably should generate summary from emit_tests target, but I am
not sure if it is working.
thanks,
-- Shuah
next prev parent reply other threads:[~2019-06-12 16:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 10:30 kselftest build broken? Dmitry Vyukov
2019-06-11 15:16 ` shuah
2019-06-11 16:03 ` Dmitry Vyukov
2019-06-11 19:20 ` shuah
2019-06-12 8:51 ` Dmitry Vyukov
2019-06-12 9:09 ` Dmitry Vyukov
2019-06-12 9:13 ` Dmitry Vyukov
2019-06-12 9:19 ` Dmitry Vyukov
2019-06-12 11:05 ` Dmitry Vyukov
2019-06-12 11:35 ` Dmitry Vyukov
2019-06-12 16:44 ` shuah [this message]
2019-06-12 18:29 ` Dmitry Vyukov
2019-06-12 19:32 ` shuah
2019-06-12 21:12 ` Daniel Díaz
2019-06-13 8:55 ` Naresh Kamboju
2019-06-13 14:10 ` shuah
2019-06-13 14:21 ` Dmitry Vyukov
2019-06-13 14:58 ` Daniel Díaz
2019-06-13 16:37 ` Dmitry Vyukov
2019-06-13 14:03 ` Dmitry Vyukov
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=1e2cc74d-a6c2-0a73-ede5-c72df28e96b2@kernel.org \
--to=shuah@kernel.org \
--cc=dvyukov@google.com \
--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