On Mon, Jun 06, 2022 at 11:24:36AM -0700, Richard Henderson wrote: > Recent runs have been taking just over the 60m default. > > Signed-off-by: Richard Henderson <richard.hender...@linaro.org> > --- > .gitlab-ci.d/custom-runners/ubuntu-20.04-s390x.yml | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/.gitlab-ci.d/custom-runners/ubuntu-20.04-s390x.yml > b/.gitlab-ci.d/custom-runners/ubuntu-20.04-s390x.yml > index 4f292a8a5b..9f1fe9e7dc 100644 > --- a/.gitlab-ci.d/custom-runners/ubuntu-20.04-s390x.yml > +++ b/.gitlab-ci.d/custom-runners/ubuntu-20.04-s390x.yml > @@ -31,6 +31,7 @@ ubuntu-20.04-s390x-all: > - s390x > variables: > DFLTCC: 0 > + timeout: 75m > rules: > - if: '$CI_PROJECT_NAMESPACE == "qemu-project" && $CI_COMMIT_BRANCH =~ > /^staging/' > - if: "$S390X_RUNNER_AVAILABLE"
I'm not entirely convinced the problem is a slow build, as opposed to a stuck test suite job. ie a genuine (non-deterministic) bug. The last few successfull builds I can see took 46 minutes which is well inside the 60 min timeout, especially considering we have a dedicated build host which should be reliable in having capacity available. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
