Linux Test Project
 help / color / mirror / Atom feed
From: Martin Doucha <mdoucha@suse.cz>
To: Petr Vorel <pvorel@suse.cz>, ltp@lists.linux.it
Subject: Re: [LTP] [v2 PATCH 2/2] dio_sparse: Set timeout 30 min
Date: Fri, 21 Jan 2022 16:25:02 +0100	[thread overview]
Message-ID: <25efba68-899f-47b1-b4f3-e6a3ddc2ff78@suse.cz> (raw)
In-Reply-To: <20220121134052.30048-2-pvorel@suse.cz>

Hi,
the commit message needs an update due to changes but otherwise:

Acked-by: Martin Doucha <mdoucha@suse.cz>

On 21. 01. 22 14:40, Petr Vorel wrote:
> Originally only ADSP075 failed (dio_sparse  -w 518192k -s 518192k -n 1000)
> but just in case increase timeout for all newly rewritten tests.
> 
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> Changes v1->v2:
> Prolong the timeout only for dio_sparse (Martin)
> 
> Kind regards,
> Petr
> 
>  testcases/kernel/io/ltp-aiodio/dio_sparse.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/testcases/kernel/io/ltp-aiodio/dio_sparse.c b/testcases/kernel/io/ltp-aiodio/dio_sparse.c
> index 39fc895d65..0039daa8d1 100644
> --- a/testcases/kernel/io/ltp-aiodio/dio_sparse.c
> +++ b/testcases/kernel/io/ltp-aiodio/dio_sparse.c
> @@ -135,4 +135,5 @@ static struct tst_test test = {
>  		"tmpfs",
>  		NULL
>  	},
> +	.timeout = 1800,
>  };


-- 
Martin Doucha   mdoucha@suse.cz
QA Engineer for Software Maintenance
SUSE LINUX, s.r.o.
CORSO IIa
Krizikova 148/34
186 00 Prague 8
Czech Republic

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  parent reply	other threads:[~2022-01-21 15:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 13:40 [LTP] [v2 PATCH 1/2] aiodio: Skip tests on tmpfs Petr Vorel
2022-01-21 13:40 ` [LTP] [v2 PATCH 2/2] dio_sparse: Set timeout 30 min Petr Vorel
2022-01-21 14:17   ` Andrea Cervesato via ltp
2022-01-21 15:25   ` Martin Doucha [this message]
2022-01-21 15:30     ` Petr Vorel
2022-01-21 14:29 ` [LTP] [v2 PATCH 1/2] aiodio: Skip tests on tmpfs Andrea Cervesato via ltp
2022-01-21 14:31   ` 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=25efba68-899f-47b1-b4f3-e6a3ddc2ff78@suse.cz \
    --to=mdoucha@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