[LTP] [PATCH] getrusage03: skip on small RAM system

Li Wang liwang@redhat.com
Mon Feb 7 13:09:25 CET 2022


On Mon, Feb 7, 2022 at 5:16 PM Jan Stancek <jstancek@redhat.com> wrote:

> On Mon, Feb 7, 2022 at 5:05 AM Li Wang <liwang@redhat.com> wrote:
> >
> > It is easy to get VmSwap increase with a small system, here is
> > run with a 1G RAM kvm guest and TBROK:
> >
> >     7   tst_test.c:1365: TINFO: Timeout per run is 0h 05m 00s
> >     8   getrusage03.c:43: TPASS: initial.self ~= child.self
> >     9   getrusage03.c:57: TPASS: initial.children ~= 100MB
> >     10  getrusage03.c:66: TPASS: child.children == 0
> >     11  getrusage03.c:84: TPASS: child.children ~= 300MB
> >     12  getrusage03.c:104: TPASS: initial.children ~= pre_wait.children
> >     13  getrusage03.c:112: TPASS: post_wait.children ~= 400MB
> >     14  getrusage03.h:25: TBROK: VmSwap is not zero
> >     15  getrusage03.c:133: TPASS: initial.children ~=
> after_zombie.children
> >     16  getrusage03.h:25: TBROK: VmSwap is not zero
> >     17  getrusage03_child.c:57: TPASS: initial.self ~= exec.self
> >     18  getrusage03_child.c:62: TPASS: initial.children ~= exec.children
> >
> > Signed-off-by: Li Wang <liwang@redhat.com>
>
> Acked-by: Jan Stancek <jstancek@redhat.com>
>
> This should fix the immediate failure, just wondering,
> would there be any downside of replacing that TBROK with TCONF?
>

I'm not quite sure. Seems it trying to test without swap happened to
guarantee less disturbing for the ’->ru_maxrss‘ counting.
TCONF looks a bit weak to attention if the regression occurs ATM.

-- 
Regards,
Li Wang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20220207/d37f22d6/attachment.htm>


More information about the ltp mailing list