From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [RFC] Reduce .runtime for Long-Running Tests ?
Date: Wed, 28 May 2025 15:35:25 +0200 [thread overview]
Message-ID: <aDcRHXhOBcqVDp05@yuki.lan> (raw)
In-Reply-To: <CAEemH2czcnak7S50--_nh5Z2Ou+rF0=5kvY7Kx_87k_X5eEj4g@mail.gmail.com>
Hi!
> After reviewing some LTP HTML test reports, I noticed that the ten tests
> alone take nearly 20 minutes to complete. For example:
>
> --------------------
> bind06 300.15s
> msgstress01 180.44s
Isn't this better after:
commit e3b85e50471b3892316a2b2c7c730e9dc8d9139e
Author: Ricardo B. Marlière <rbm@suse.com>
Date: Wed May 21 05:31:12 2025 -0300
syscalls/msgstress01: Set upper bound for num_messages
> fsx22 170.47s
> pty07 150.04s
> pty06 150.02s
> gf18 121.09s
> gf17 120.82s
> gf16 120.13s
> dirtyc0w_shmem 120.11s
> setsockopt07 76.47s
As Peter pointed out, most of these are fuzzy sync tests and the runtime
is callibrated in order to get reasonable chance of reproducing the
results. But indeed the runtime does not scale with the speed of the
machine and we are not setting the pair exec_loops in the tests that run
for so long, so I suppose that callibrating the number of loops for
these tests that does not make the bug less reproducible would make
things better.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-05-28 13:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 11:00 [LTP] [RFC] Reduce .runtime for Long-Running Tests ? Li Wang via ltp
2025-05-27 11:10 ` Petr Vorel
2025-05-27 11:18 ` Li Wang via ltp
2025-05-27 11:11 ` Li Wang via ltp
2025-05-27 11:19 ` Cyril Hrubis
2025-05-27 11:28 ` Andrea Cervesato via ltp
2025-05-27 11:56 ` Cyril Hrubis
2025-05-28 13:35 ` Cyril Hrubis [this message]
2025-05-28 13:49 ` Martin Doucha
2025-05-29 1:53 ` Li Wang via ltp
2025-06-20 5:48 ` Li Wang via ltp
2025-06-20 9:04 ` Cyril Hrubis
2025-06-20 9:23 ` Li Wang via ltp
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=aDcRHXhOBcqVDp05@yuki.lan \
--to=chrubis@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
/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.