From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] TWARN and "ltp-pan reported PASS"
Date: Wed, 10 May 2017 11:04:28 +0200 [thread overview]
Message-ID: <20170510090428.GC29838@rei.suse.de> (raw)
In-Reply-To: <20170509120935.q2v6dqhwmecy265w@dell5510>
Hi!
> our shell scripts wrapping ltp-pan binary report failure when there is any TWARN.
>
> Similar code in these scripts:
> runltp
> runltplite.sh
> testscripts/diskio.sh
> testscripts/network.sh
> testscripts/runEALtests.sh
>
> if [ $? -eq "0" ]; then
> echo ltp-pan reported PASS
> else
> echo ltp-pan reported FAIL
> fi
>
> Does using TWARN always always mean failure? I mean, it's good that ltp-pan returns 4
> instead of 0, but wrapper script should return something like:
>
> if [ $? -eq 0 ]; then
> echo ltp-pan reported PASS
> elif [ $? -eq 4 ]; then
> echo ltp-pan reported PASS with warnings
> else
> echo ltp-pan reported FAIL
> fi
Are you sure that ltp-pan actually passes the test return value? As far
as I can tell it actually increments the exit_stat variable on error
then does exit(exit_stat).
So I would say that the only guarantee that you have is that non-zero
return value from ltp-pan means "everything went ok" and non-zero
"something went wrong".
Frankly at this point I would rather kept the old test execution scripts
as they are and put more effort into the new execution framework.
Hopefully I will have a bit time to invest into it once we are done with
the release.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-05-10 9:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 12:09 [LTP] TWARN and "ltp-pan reported PASS" Petr Vorel
2017-05-10 9:04 ` Cyril Hrubis [this message]
2017-05-10 10:15 ` Petr Vorel
2017-05-17 13:41 ` Cyril Hrubis
2017-05-18 10:42 ` Petr Vorel
2017-05-18 11:15 ` Cyril Hrubis
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=20170510090428.GC29838@rei.suse.de \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.