All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: Martin Doucha <martin.doucha@suse.com>,
	lkft@linaro.org, lkft-triage@lists.linaro.org,
	LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [REGRESSION] lkft ltp for cea142b
Date: Mon, 19 Sep 2022 10:28:06 +0200	[thread overview]
Message-ID: <YygoFpOWW4Cuh2BB@yuki> (raw)
In-Reply-To: <CAEemH2cLKhrE5SVjfd5Got3adf9+C0dJeuP-qY_r98fDUr2gMQ@mail.gmail.com>

Hi!
> > tst_pollute_memory() consume time is proportional to the amount of
> > free RAM, it is hard to find one fixed value of max_runtime to fit all test
> > platforms.
> >
> > From my experience, if you limited this test only run with small
> > machine (e.g. RAM <= 32G), that performs well with whatever
> > bare metal or VM, no timeout ever.
> >
> 
> Btw, we did that by setting a test filter before LTP running, also we could
> add a field .max_mem_avail to tst_test struct for achieving that, but not
> sure if it's worth doing that at this moment.

The proper solution will be adding a separate timeouts for setup/cleanup
and limiting the setup runtime to something sensible, but that is
something for the next development cycle.

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-09-19  8:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-17 12:00 [LTP] [REGRESSION] lkft ltp for cea142b lkft
2022-09-19  3:13 ` Petr Vorel
2022-09-19  3:27   ` Li Wang
2022-09-19  3:35     ` Li Wang
2022-09-19  8:28       ` Cyril Hrubis [this message]
2022-09-19  8:39         ` Li Wang
2022-09-19  8:50           ` Cyril Hrubis
2022-09-19  8:57   ` Martin Doucha
2022-09-19 12:57     ` Petr Vorel

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=YygoFpOWW4Cuh2BB@yuki \
    --to=chrubis@suse.cz \
    --cc=liwang@redhat.com \
    --cc=lkft-triage@lists.linaro.org \
    --cc=lkft@linaro.org \
    --cc=ltp@lists.linux.it \
    --cc=martin.doucha@suse.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 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.