From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4 2/5] tst_test.c: Add tst_multiply_timeout()
Date: Mon, 21 Oct 2019 14:50:53 +0200 [thread overview]
Message-ID: <20191021125053.GA18513@x230> (raw)
In-Reply-To: <20191018124502.25599-3-cfamullaconrad@suse.de>
Hi Clements,
> + if (timeout_mul < 1)
> + tst_brk(TBROK, "LTP_TIMEOUT_MUL must to be int >= 1! (%d)",
> + timeout_mul);
> +
> + if (timeout < 1)
> + tst_brk(TBROK, "timeout must to be >= 1! (%d)", timeout);
> +
> + return timeout * timeout_mul;
> +}
> +void tst_set_timeout(int timeout)
> +{
> if (timeout == -1) {
> tst_res(TINFO, "Timeout per run is disabled");
> return;
> }
> - results->timeout = timeout;
> + if (timeout < 1)
> + tst_brk(TBROK, "timeout need to be >= 1! (%d)", timeout);
need => needs, but better to use must (to be consistent with the previous one:
tst_brk(TBROK, "timeout must to be >= 1! (%d)", timeout);
I also wonder, if this check is needed, next step is
results->timeout = tst_multiply_timeout(timeout);
which does the same check.
Can be changed with the committer (unless you plan to do v5 for some reason).
> - if (mul) {
> - float m = atof(mul);
> -
> - if (m < 1)
> - tst_brk(TBROK, "Invalid timeout multiplier '%s'", mul);
> -
> - results->timeout = results->timeout * m + 0.5;
> - }
> + results->timeout = tst_multiply_timeout(timeout);
> tst_res(TINFO, "Timeout per run is %uh %02um %02us",
> results->timeout/3600, (results->timeout%3600)/60,
Kind regards,
Petr
next prev parent reply other threads:[~2019-10-21 12:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 12:44 [LTP] [PATCH v4 0/5] tst_test.sh: Use LTP_TIMEOUT_MUL in TST_RETRY_FN() Clemens Famulla-Conrad
2019-10-18 12:44 ` [LTP] [PATCH v4 1/5] " Clemens Famulla-Conrad
2019-10-21 12:42 ` Petr Vorel
2019-10-21 14:18 ` Clemens Famulla-Conrad
2019-10-18 12:44 ` [LTP] [PATCH v4 2/5] tst_test.c: Add tst_multiply_timeout() Clemens Famulla-Conrad
2019-10-21 12:50 ` Petr Vorel [this message]
2019-10-21 14:17 ` Clemens Famulla-Conrad
2019-10-21 14:42 ` Petr Vorel
2019-10-22 13:14 ` Petr Vorel
2019-10-21 14:37 ` Cyril Hrubis
2019-10-21 15:31 ` Clemens Famulla-Conrad
2019-10-21 18:08 ` Petr Vorel
2019-10-18 12:45 ` [LTP] [PATCH v4 3/5] tst_common.h: Use tst_multiply_timeout in TST_RETRY_FN() Clemens Famulla-Conrad
2019-10-21 14:38 ` Cyril Hrubis
2019-10-18 12:45 ` [LTP] [PATCH v4 4/5] Add newlib shell test for tst_multiply_timeout() Clemens Famulla-Conrad
2019-10-21 9:28 ` Li Wang
2019-10-22 8:08 ` Petr Vorel
2019-10-22 12:31 ` Clemens Famulla-Conrad
2019-10-18 12:45 ` [LTP] [PATCH v4 5/5] Adopt doc for TST_RETRY_FUNC for LTP_TIMEOUT_MUL Clemens Famulla-Conrad
2019-10-21 9:41 ` Richard Palethorpe
2019-10-21 13:15 ` Petr Vorel
2019-10-21 13:41 ` Clemens Famulla-Conrad
2019-10-21 13:53 ` Petr Vorel
2019-10-21 14:46 ` Cyril Hrubis
2019-10-21 18:10 ` Petr Vorel
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=20191021125053.GA18513@x230 \
--to=pvorel@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