From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] Increase .max_runtime for fsx-linux
Date: Wed, 24 Jan 2024 15:07:10 +0100 [thread overview]
Message-ID: <20240124140710.GA299755@pevik> (raw)
In-Reply-To: <ZbELTkR4RJXKduP2@yuki>
> Hi!
> I've added:
The longest run is due:
fsx22 fsx-linux -N 100000
other runs are much faster. I hope that -N 100000 makes sense, because I was
thinking about deleting this test. Because allow test to run for 1 hour can lead
to masive runtime in case of kernel bug which keeps fsx-linux running (22 hours
in worse case).
Yes, 60 sec is too low (-N 100000 runs on my VM 50 sec, which is not much
spare time), but maybe adding just 300 (5 min) or 600 should have been enough
even for -N 100000 (all 21 previous tests run faster).
Don't we want to reconsider smaller value?
> Fixes: 176667f40710 ("fsx-linux: Add .max_runtime = 60")
FYI The first commit which introduce the problem was rewrite into new API
134b08362 ("fs: Rewrite fsx-linux test")
Kind regards,
Petr
> To the commit message and pushed, thanks.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2024-01-24 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 10:23 [LTP] [PATCH v1] Increase .max_runtime for fsx-linux Andrea Cervesato
2024-01-24 13:06 ` Cyril Hrubis
2024-01-24 14:07 ` Petr Vorel [this message]
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=20240124140710.GA299755@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox