From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 1/1] swapoff01: Define max_runtime 45s
Date: Wed, 4 Sep 2024 10:52:11 +0200 [thread overview]
Message-ID: <Ztgfu4bTVyw7hvdP@yuki.lan> (raw)
In-Reply-To: <20240904053157.GA836933@pevik>
Hi!
> > So yes it looks like the actual test needs some runtime defined,
> > although I'm not sure how long it should be. We probably need a
> > reference machine to callibrate this on. I would avoid any emulated CPU
> > and choose a real hardware. I guess one of the RPis e.g. Pi Zero would
> > be a good choice since they are widely available and slow by any modern
> > standards.
>
> This makes sense.
So I dusted off my Pi Zero and indeed the test timeouts there as well.
The ntfs filesystem takes 78s, ext2 29s, exfat 20s. So I would say that
max_runtime should be at least a minute. I guess I will try to run the
whole run there before the release and check for timeouts so that we are
sure that the runtime is set reasonably even for very slow hardware.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-09-04 8:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 14:03 [LTP] [PATCH v2 1/1] swapoff01: Define max_runtime 45s Petr Vorel
2024-09-03 15:15 ` Cyril Hrubis
2024-09-04 5:31 ` Petr Vorel
2024-09-04 8:52 ` Cyril Hrubis [this message]
2024-09-04 9:26 ` Li Wang
2024-09-04 9:37 ` Li Wang
2024-09-04 10:07 ` Petr Vorel
2024-09-04 13:58 ` Cyril Hrubis
2024-09-07 2:05 ` Li Wang
2024-09-09 2:52 ` [LTP] [PATCH v3] swapoff01/swapon01: Define max_runtime 1 mins Li Wang
2024-09-09 11:05 ` Avinesh Kumar
2024-09-09 11:46 ` Jan Stancek
2024-09-09 12:54 ` Cyril Hrubis
2024-09-09 14:02 ` 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=Ztgfu4bTVyw7hvdP@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@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