From: Hiraku Toyooka <hiraku.toyooka.gu@hitachi.com>
To: Kees Cook <keescook@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Tony Luck <tony.luck@intel.com>,
Linux API <linux-api@vger.kernel.org>,
Anton Vorontsov <anton@enomsg.org>,
Shuah Khan <shuahkh@osg.samsung.com>,
Mark Salyzyn <salyzyn@android.com>,
Colin Cross <ccross@android.com>, <seiji.aguchi.tr@hitachi.com>
Subject: Re: [PATCH 2/2] selftests/pstore: add pstore test scripts going with reboot
Date: Tue, 15 Sep 2015 11:41:39 +0900 [thread overview]
Message-ID: <55F78563.50006@hitachi.com> (raw)
In-Reply-To: <CAGXu5j+Ha0t-acFc+morgUiDRCHGdx8QHySX29PYpnj4QFiJhA@mail.gmail.com>
Hello Kees,
>> +run_crash:
>> + @sh pstore_crash_test || echo "pstore_crash_test: [FAIL]"
>
> This is probably better written to exit 1 on failure, otherwise it
> just _says_ it fails. (Though lots of selftests in the tree already
> have this problem, it's best to avoid the pattern for new stuff.)
> Maybe something like:
>
> @sh pstore_crash_test || { echo "pstore_crash_test: [FAIL]";
exit 1; }
OK. I'll add the "exit 1".
>> +prlog -n "Checking dmesg files exist in pstore filesystem ... "
>> +if [ -e dmesg-${backend}-0 ]; then
>> + prlog "ok"
>> + for f in `ls dmesg-${backend}-*`; do
>> + prlog -e "\t${f}"
>> + done
>> +else
>> + prlog "FAIL"
>> + rc=1
>> +fi
>
> This test pattern is repeated a lot. Maybe better to create a helper
> function instead? It could make the tests much more readable.
Yes, I should make a helper function in v2.
Best regards,
Hiraku Toyooka
next prev parent reply other threads:[~2015-09-15 2:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 11:06 [PATCH 0/2] selftests/pstore: add pstore test script Hiraku Toyooka
2015-09-08 11:06 ` [PATCH 1/2] selftests/pstore: add pstore test script for pre-reboot Hiraku Toyooka
2015-09-08 23:22 ` Mark Salyzyn
2015-09-15 2:30 ` Hiraku Toyooka
2015-09-21 21:04 ` Mark Salyzyn
2015-09-29 7:18 ` Hiraku Toyooka
2015-09-08 23:37 ` Kees Cook
2015-09-15 2:31 ` Hiraku Toyooka
2015-09-16 12:02 ` 阿口誠司 / AGUCHI,SEIJI
2015-09-17 5:54 ` Hiraku Toyooka
2015-09-08 11:06 ` [PATCH 2/2] selftests/pstore: add pstore test scripts going with reboot Hiraku Toyooka
2015-09-08 23:40 ` Kees Cook
2015-09-15 2:41 ` Hiraku Toyooka [this message]
2015-09-16 12:11 ` 阿口誠司 / AGUCHI,SEIJI
2015-09-17 5:54 ` Hiraku Toyooka
2015-09-08 23:42 ` [PATCH 0/2] selftests/pstore: add pstore test script Kees Cook
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=55F78563.50006@hitachi.com \
--to=hiraku.toyooka.gu@hitachi.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=salyzyn@android.com \
--cc=seiji.aguchi.tr@hitachi.com \
--cc=shuahkh@osg.samsung.com \
--cc=tony.luck@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
Powered by JetHome