ltp.lists.linux.it archive mirror
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 04/10] ioctl_sg01: Set unlimited max_runtime
Date: Tue, 30 Aug 2022 20:38:43 +0200	[thread overview]
Message-ID: <Yw5ZM3y5VbHJ4lgQ@yuki> (raw)
In-Reply-To: <78c5ee4c-6100-94ea-e2de-38f16f0d2b0f@suse.cz>

Hi!
> >> Test setup can take very long time depending on the amount of free RAM.
> >> Set unlimited max_runtime to avoid timeout issues.
> > 
> > I would rather go for large enough number e.g. 30 minutes than
> > unlimited as the unlimited runtime turns off the timeouts and such test
> > can run undefinitely.
> 
> Even setting max_runtime is an ugly hack here because the test itself is 
> nearly instant. The setup() function is what actually times out. But 
> there's currently no way to change the default 30 second timeout 
> allocated for setup() and cleanup(). It'd be much better if I could set 
> that setup() has unlimited timeout and the test itself is limited to 5 
> seconds.

I guess that we can add setup_max_runtime and cleanup_max_runtime
however I would still set the setup_max_runtime to a large but finite
value here.

-- 
Cyril Hrubis
chrubis@suse.cz

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

  reply	other threads:[~2022-08-30 18:37 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 13:49 [LTP] [PATCH 00/10] Max_runtime and other minor fixes Martin Doucha
2022-08-30 13:49 ` [LTP] [PATCH 01/10] syscalls/pty06: Add CVE reference Martin Doucha
2022-08-30 14:40   ` Cyril Hrubis
2022-08-30 13:49 ` [LTP] [PATCH 02/10] cve-2017-2671: Increase max_runtime Martin Doucha
2022-08-30 14:40   ` Cyril Hrubis
2022-08-30 13:50 ` [LTP] [PATCH 03/10] ksm: Add max_runtime to tests Martin Doucha
2022-08-30 14:49   ` Cyril Hrubis
2022-08-31 12:45     ` Martin Doucha
2022-08-31 12:50       ` Cyril Hrubis
2022-08-31 12:54         ` Martin Doucha
2022-09-05 16:14           ` Petr Vorel
2022-09-09  8:28             ` Cyril Hrubis
2022-08-30 13:50 ` [LTP] [PATCH 04/10] ioctl_sg01: Set unlimited max_runtime Martin Doucha
2022-08-30 15:16   ` Cyril Hrubis
2022-08-30 15:23     ` Martin Doucha
2022-08-30 18:38       ` Cyril Hrubis [this message]
2022-08-30 13:50 ` [LTP] [PATCH 05/10] csf_bandwidth01: Add max_runtime Martin Doucha
2022-08-30 15:30   ` Cyril Hrubis
2022-08-30 13:50 ` [LTP] [PATCH 06/10] copy_file_range01: " Martin Doucha
2022-08-31  8:21   ` Petr Vorel
2022-08-31  9:06     ` Martin Doucha
2022-08-31  9:25       ` Cyril Hrubis
2022-08-31 12:19         ` Petr Vorel
2022-08-31  9:06     ` Cyril Hrubis
2022-08-31 12:18       ` Petr Vorel
2022-08-31  9:22   ` Cyril Hrubis
2022-08-30 13:50 ` [LTP] [PATCH 07/10] perf_event_open02: " Martin Doucha
2022-08-31  8:23   ` Petr Vorel
2022-08-31 10:07   ` Cyril Hrubis
2022-08-30 13:50 ` [LTP] [PATCH 08/10] readahead02: " Martin Doucha
2022-08-31  9:29   ` Petr Vorel
2022-08-31 11:29   ` Cyril Hrubis
2022-08-30 13:50 ` [LTP] [PATCH 09/10] request_key03: " Martin Doucha
2022-08-31  9:45   ` Petr Vorel
2022-08-31  9:47   ` Petr Vorel
2022-08-31 12:24   ` Cyril Hrubis
2022-08-30 13:50 ` [LTP] [PATCH 10/10] sendfile09: " Martin Doucha
2022-08-31  9:48   ` Petr Vorel
2022-08-31 12:59   ` Jan Stancek

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=Yw5ZM3y5VbHJ4lgQ@yuki \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=mdoucha@suse.cz \
    /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;
as well as URLs for NNTP newsgroup(s).