From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] preadv203: set max_runtime to 270s
Date: Wed, 25 May 2022 14:51:24 +0800 [thread overview]
Message-ID: <20220525065124.2665801-1-liwang@redhat.com> (raw)
In-Reply-To: <YozXG/f0HHSrhm9E@yuki>
Before the runtime patchset preadv203 use 5min as default timeout
per fs, that's really long enough for prepare_device(). But after
that, its now only has 30s which might be short for a slower system
to do preparation work.
Let's set max_runtime to 270s to make the timeout at least equal
to previously.
==== Before =====
# ./preadv203
...
tst_test.c:1459: TINFO: Timeout per run is 0h 05m 00s
preadv203.c:143: TINFO: Number of full_reads 2567, short reads 10, zero len reads 0, EAGAIN(s) 2530185
preadv203.c:180: TINFO: Number of writes 682740
preadv203.c:194: TINFO: Cache dropped 114 times
preadv203.c:223: TPASS: Got some EAGAIN
tst_test.c:1531: TINFO: Testing on ext3
tst_test.c:999: TINFO: Formatting /dev/loop0 with ext3 opts='' extra opts=''
mke2fs 1.46.5 (30-Dec-2021)
tst_test.c:1459: TINFO: Timeout per run is 0h 05m 00s
...
==== After =====
# time ./preadv203
tst_device.c:89: TINFO: Found free device 0 '/dev/loop0'
tst_test.c:1524: TINFO: Timeout per run is 0h 00m 30s
tst_supported_fs_types.c:89: TINFO: Kernel supports ext2
...
tst_test.c:1597: TINFO: Testing on ext2
tst_test.c:1062: TINFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
mke2fs 1.46.5 (30-Dec-2021)
Test timeouted, sending SIGKILL!
tst_test.c:1575: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1
tst_test.c:1577: TBROK: Test killed! (timeout?)
Summary:
passed 0
failed 0
broken 1
skipped 0
warnings 0
real 0m36.246s
user 0m0.706s
sys 1m2.965s
Signed-off-by: Li Wang <liwang@redhat.com>
Cc: Cyril Hrubis <chrubis@suse.cz>
---
Notes:
Another fixe way is going with define DEFAULT_TIMEOUT to 60, that
generally extends all timeout for each fs to perform prepare_device().
And this will impact all test cases with setting .all_filesystems.
testcases/kernel/syscalls/preadv2/preadv203.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/testcases/kernel/syscalls/preadv2/preadv203.c b/testcases/kernel/syscalls/preadv2/preadv203.c
index 01622ad15..46bb39ef1 100644
--- a/testcases/kernel/syscalls/preadv2/preadv203.c
+++ b/testcases/kernel/syscalls/preadv2/preadv203.c
@@ -279,5 +279,6 @@ static struct tst_test test = {
.mntpoint = MNTPOINT,
.mount_device = 1,
.all_filesystems = 1,
+ .max_runtime = 270,
.needs_root = 1,
};
--
2.31.1
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-05-25 6:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 12:50 [LTP] LTP release preparations Cyril Hrubis
2022-05-09 13:51 ` Petr Vorel
2022-05-10 8:36 ` Li Wang
2022-05-10 13:54 ` Cyril Hrubis
2022-05-19 11:42 ` Martin Doucha
2022-05-19 12:11 ` Cyril Hrubis
2022-05-24 13:01 ` Cyril Hrubis
2022-05-25 6:51 ` Li Wang [this message]
2022-05-25 8:21 ` [LTP] [PATCH] preadv203: set max_runtime to 270s Cyril Hrubis
2022-05-25 10:16 ` 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=20220525065124.2665801-1-liwang@redhat.com \
--to=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.