[kvm-unit-tests] x86/unittests.cfg: Increase the timeout of the sieve test to 180s
diff mbox series

Message ID 20190923111210.9495-1-thuth@redhat.com
State New
Headers show
Series
  • [kvm-unit-tests] x86/unittests.cfg: Increase the timeout of the sieve test to 180s
Related show

Commit Message

Thomas Huth Sept. 23, 2019, 11:12 a.m. UTC
In the gitlab-CI (where we are running the tests with TCG), the sieve
test sometimes takes more than 90s to finish, and thus fails due
to the 90s timeout from scripts/runtime.bash. Increase the timeout
for this test to make it always succeed.

Signed-off-by: Thomas Huth <thuth@redhat.com>
---
 See for example this run here where it took more than 90s:
 
  https://gitlab.com/huth/kvm-unit-tests/-/jobs/301407814
 
 If you don't like the change in unittests.cfg, I can also tweak
 the (global) timeout in .gitlab-ci.yml instead.

 x86/unittests.cfg | 1 +
 1 file changed, 1 insertion(+)

Comments

Thomas Huth Nov. 15, 2019, 10:36 a.m. UTC | #1
On 23/09/2019 13.12, Thomas Huth wrote:
> In the gitlab-CI (where we are running the tests with TCG), the sieve
> test sometimes takes more than 90s to finish, and thus fails due
> to the 90s timeout from scripts/runtime.bash. Increase the timeout
> for this test to make it always succeed.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  See for example this run here where it took more than 90s:
>  
>   https://gitlab.com/huth/kvm-unit-tests/-/jobs/301407814
>  
>  If you don't like the change in unittests.cfg, I can also tweak
>  the (global) timeout in .gitlab-ci.yml instead.
> 
>  x86/unittests.cfg | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/x86/unittests.cfg b/x86/unittests.cfg
> index 694ee3d..e951629 100644
> --- a/x86/unittests.cfg
> +++ b/x86/unittests.cfg
> @@ -172,6 +172,7 @@ file = s3.flat
>  
>  [sieve]
>  file = sieve.flat
> +timeout = 180
>  
>  [syscall]
>  file = syscall.flat
> 

Ping?

 Thomas
Paolo Bonzini Nov. 15, 2019, 11:43 a.m. UTC | #2
On 23/09/19 13:12, Thomas Huth wrote:
> In the gitlab-CI (where we are running the tests with TCG), the sieve
> test sometimes takes more than 90s to finish, and thus fails due
> to the 90s timeout from scripts/runtime.bash. Increase the timeout
> for this test to make it always succeed.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  See for example this run here where it took more than 90s:
>  
>   https://gitlab.com/huth/kvm-unit-tests/-/jobs/301407814
>  
>  If you don't like the change in unittests.cfg, I can also tweak
>  the (global) timeout in .gitlab-ci.yml instead.
> 
>  x86/unittests.cfg | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/x86/unittests.cfg b/x86/unittests.cfg
> index 694ee3d..e951629 100644
> --- a/x86/unittests.cfg
> +++ b/x86/unittests.cfg
> @@ -172,6 +172,7 @@ file = s3.flat
>  
>  [sieve]
>  file = sieve.flat
> +timeout = 180
>  
>  [syscall]
>  file = syscall.flat
> 

Queued, thanks.

Paolo

Patch
diff mbox series

diff --git a/x86/unittests.cfg b/x86/unittests.cfg
index 694ee3d..e951629 100644
--- a/x86/unittests.cfg
+++ b/x86/unittests.cfg
@@ -172,6 +172,7 @@  file = s3.flat
 
 [sieve]
 file = sieve.flat
+timeout = 180
 
 [syscall]
 file = syscall.flat