[LTP] [PATCH 2/3] lib/test.sh: TCONF needs to be counted
Caspar Zhang
caspar@linux.alibaba.com
Sun Jun 9 17:40:38 CEST 2019
On Fri, May 31, 2019 at 11:17:14AM +0800, Li Wang wrote:
>
>
> On Thu, May 30, 2019 at 5:10 PM Caspar Zhang <[1]caspar@linux.alibaba.com>
> wrote:
>
> TCONF should also be one of exit statuses in a single test, else the
> output of TST_COUNT in shell tests could be wrong.
>
> Wrong:
> <<<test_output>>>
> memcg_use_hierarchy_test 1 TINFO: Starting test 1
> memcg_use_hierarchy_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0
> failed
> memcg_use_hierarchy_test 1 TPASS: process 28658 is killed
> memcg_use_hierarchy_test 2 TINFO: Starting test 2
> memcg_use_hierarchy_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0
> failed
> memcg_use_hierarchy_test 2 TCONF: memory.use_hierarchy already been 1,
> blame systemd, skip
> memcg_use_hierarchy_test 2 TINFO: Starting test 3
> memcg_use_hierarchy_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0
> failed
> memcg_use_hierarchy_test 2 TPASS: echo 0 > subgroup/memory.use_hierarchy
> failed as expected
> <<<execution_status>>>
>
> Right:
> <<<test_output>>>
> memcg_use_hierarchy_test 1 TINFO: Starting test 1
> memcg_use_hierarchy_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0
> failed
> memcg_use_hierarchy_test 1 TPASS: process 26825 is killed
> memcg_use_hierarchy_test 2 TINFO: Starting test 2
> memcg_use_hierarchy_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0
> failed
> memcg_use_hierarchy_test 2 TCONF: memory.use_hierarchy already been 1,
> blame systemd, skip
> memcg_use_hierarchy_test 3 TINFO: Starting test 3
> memcg_use_hierarchy_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0
> failed
> memcg_use_hierarchy_test 3 TPASS: echo 0 > subgroup/memory.use_hierarchy
> failed as expected
> <<<execution_status>>>
>
>
> This is a good catch, but maybe it's not wise to simply regard the TCONF as a
> single test, because there are many system-config detections in setup()
> function, that will make LTP gives a mendacious report on the test numbers if
> applying this patch.
>
> e.g.
>
> if tst_kvcmp -lt "3.10"; then
> Â Â tst_brk TCONF "test must be run with kernel 3.10 or newer"
> fi
> if dir path not exist; then
> Â Â tst_brk TCONF "system does not have xxxx/"
> fi
> and so on...
TCONF usually report only once, I would still take it a valid report on
numbers. Take your case as example, I guess we are able to see results
like:
mytest 1 TPASS: pass
or
mytest 1 TCONF: test must be run with kernel 3.10 or newer
or
mytest 1 TCONF: system does not have xxx/
Thanks,
Caspar
>
> Â
>
>
> Signed-off-by: Caspar Zhang <[2]caspar@linux.alibaba.com>
> ---
> Â testcases/lib/test.sh | 3 +--
> Â 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/testcases/lib/test.sh b/testcases/lib/test.sh
> index 670248ee5..ade8fcdff 100644
> --- a/testcases/lib/test.sh
> +++ b/testcases/lib/test.sh
> @@ -58,8 +58,7 @@ tst_resm()
> Â Â Â Â echo " $@"
>
> Â Â Â Â case "$ret" in
> -Â Â Â Â TPASS|TFAIL)
> -Â Â Â Â TST_COUNT=$((TST_COUNT+1));;
> +Â Â Â Â TPASS|TFAIL|TCONF) TST_COUNT=$((TST_COUNT+1));;
> Â Â Â Â esac
> Â }
>
> --
> 2.21.0
>
>
> --
> Mailing list info: [3]https://lists.linux.it/listinfo/ltp
>
>
>
> --
> Regards,
> Li Wang
>
> References:
>
> [1] mailto:caspar@linux.alibaba.com
> [2] mailto:caspar@linux.alibaba.com
> [3] https://lists.linux.it/listinfo/ltp
--
Thanks,
Caspar
More information about the ltp
mailing list