public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: Philip Auld <pauld@redhat.com>, ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH] starvation: set a baseline for maximum runtime
Date: Wed, 27 Nov 2024 11:40:23 +0100	[thread overview]
Message-ID: <Z0b3F2PHzRZq8WeL@yuki.lan> (raw)
In-Reply-To: <CAEemH2cJmBra=SajChZ-KKe9GimCBtdvwcnWNiwEz2dHFP8f4Q@mail.gmail.com>

Hi!
> After thinking it over, I guess we'd better _only_ apply this method
> to some special slow tests (aka. more easily timeout tests). If we do
> the examination of those kernel options in the library for all, that
> maybe a burden to most quick tests, which always finish in a few
> seconds (far less than the default 30s).
> 
> Therefore, I came up with a new option for .max_runtime, which is
> TST_DYNAMICAL_RUNTIME. Similar to the TST_UNLIMITED_RUNTIME
> we ever use. Test by adding this .max_runtime = TST_DYNAIMCAL_RUNTIME
> that will try to find a proper timeout value in the running time for the
> test.

I was thinking to only multiply the max_runtime defined by the test in
the library. That way only slow tests that set the max_runtime would be
affected.

-- 
Cyril Hrubis
chrubis@suse.cz

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

  reply	other threads:[~2024-11-27 10:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 10:04 [LTP] [RFC PATCH] starvation: set a baseline for maximum runtime Li Wang
2024-11-26 10:28 ` Cyril Hrubis
2024-11-26 10:59   ` Li Wang
2024-11-26 11:23     ` Cyril Hrubis
2024-11-27  4:15       ` Li Wang
2024-11-27  7:48         ` [LTP] [Draft PATCH] lib: add TST_DYNAMICAL_RUNTIME option Li Wang
2024-11-27  8:21           ` Li Wang
2024-11-27  9:46         ` [LTP] [RFC PATCH] starvation: set a baseline for maximum runtime Cyril Hrubis
2024-11-27 10:08           ` Li Wang
2024-11-27 10:40             ` Cyril Hrubis [this message]
2024-11-27 10:56               ` Li Wang

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=Z0b3F2PHzRZq8WeL@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=pauld@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox