Re: [RFC PATCH v2 4/4] ftracetest: Add XFAIL/XPASS/UNSUPPORTED as result code

2014-09-01 Thread Masami Hiramatsu
(2014/08/26 20:15), Masami Hiramatsu wrote: > @@ -132,11 +163,9 @@ run_test() { # testfile >echo "execute: "$1 > $testlog >(cd $TRACING_DIR; set -x ; source $t) >> $testlog 2>&1 >ret=$? > - if [ $ret -ne 0 ]; then > -failed > -catlog $testlog > - else > -passed > + eval_r

Re: [RFC PATCH v2 4/4] ftracetest: Add XFAIL/XPASS/UNSUPPORTED as result code

2014-08-31 Thread Masami Hiramatsu
(2014/08/29 10:05), Shuah Khan wrote: > On 08/26/2014 05:15 AM, Masami Hiramatsu wrote: >> Add XFAIL, XPASS and UNSUPPORTED as a result code. These are >> used for the results that test case is expected to fail or >> unsupported feature (by config). >> This also introduces PASS/FAIL/XFAIL/XPASS/UNS

Re: [RFC PATCH v2 4/4] ftracetest: Add XFAIL/XPASS/UNSUPPORTED as result code

2014-08-28 Thread Shuah Khan
On 08/26/2014 05:15 AM, Masami Hiramatsu wrote: > Add XFAIL, XPASS and UNSUPPORTED as a result code. These are > used for the results that test case is expected to fail or > unsupported feature (by config). > This also introduces PASS/FAIL/XFAIL/XPASS/UNSUP result codes > for each testcase. Since t