Message ID | 20190923111210.9495-1-thuth@redhat.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [kvm-unit-tests] x86/unittests.cfg: Increase the timeout of the sieve test to 180s | expand |
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
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
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
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(+)