From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id E4FF8CA0ED4 for ; Tue, 12 Sep 2023 13:53:21 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qg3ot-0000aO-1T; Tue, 12 Sep 2023 09:52:47 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qg3or-0000aC-KU for qemu-devel@nongnu.org; Tue, 12 Sep 2023 09:52:45 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qg3on-0006ZZ-BM for qemu-devel@nongnu.org; Tue, 12 Sep 2023 09:52:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1694526759; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=e2T5WQ948cyB2ziRux/FfCLUDY5EDltOY8EPp4/UZq8=; b=OPYITA2IKoi8EXszv9P07HS943LOIjYHFbJAi3v9XJJEzyzhRIiPSh0KCWtAt0kzJ6/u9Q Io15o4+v9aPtEbQox0ihQewdc+XKP2aqdMKBZcJmTxhwND+82wRc7LskzYbLgrMJArLGgq vufZUC6vOK3XnmahZhlNmyhRl+CV6TE= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-399-ZQyCLC7hM8q8aZ_gq8kvbQ-1; Tue, 12 Sep 2023 09:52:35 -0400 X-MC-Unique: ZQyCLC7hM8q8aZ_gq8kvbQ-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 6BF2C101FAAB; Tue, 12 Sep 2023 13:52:35 +0000 (UTC) Received: from redhat.com (unknown [10.42.28.38]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 2AD6C40C6EA8; Tue, 12 Sep 2023 13:52:34 +0000 (UTC) Date: Tue, 12 Sep 2023 14:52:31 +0100 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Stefan Hajnoczi Cc: qemu-devel@nongnu.org, Thomas Huth , Beraldo Leal , Alex =?utf-8?Q?Benn=C3=A9e?= , Philippe =?utf-8?Q?Mathieu-Daud=C3=A9?= , Wainer dos Santos Moschetta Subject: Re: [PATCH] gitlab-ci/cirrus: Increase timeout to 100 minutes Message-ID: References: <20230912133829.61352-1-stefanha@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20230912133829.61352-1-stefanha@redhat.com> User-Agent: Mutt/2.2.9 (2022-11-12) X-Scanned-By: MIMEDefang 3.1 on 10.11.54.2 Received-SPF: pass client-ip=170.10.129.124; envelope-from=berrange@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org On Tue, Sep 12, 2023 at 09:38:29AM -0400, Stefan Hajnoczi wrote: > The 80m timeout is not enough: > > 672/832 qemu:block / io-qcow2-041 OK 39.77s 1 subtests passed > Timed out! IIUC, that 'timed out' message is coming from Cirrus CI logs, which we can see over on the cirrus task: https://cirrus-ci.com/task/6462328380588032 > https://gitlab.com/qemu-project/qemu/-/jobs/5058610599 This reports duration "64 minutes", vs a GitLab timeout of 1hr20. IOW, we're not hitting the gitlab timeout, we're hitting hte Cirrus CI timeout, which defaults to 60 minutes. The other 4 minuts gitlab reports is likely because Cirrus queued the job for 4 minutes before starting execution. > > Buglink: https://gitlab.com/qemu-project/qemu/-/issues/1882 > Fixes: d06f3bf92267 ("gitlab-ci/cirrus: Increase timeout to 80 minutes") > Signed-off-by: Stefan Hajnoczi > --- > .gitlab-ci.d/cirrus.yml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/.gitlab-ci.d/cirrus.yml b/.gitlab-ci.d/cirrus.yml > index 41d64d6680..d19633f758 100644 > --- a/.gitlab-ci.d/cirrus.yml > +++ b/.gitlab-ci.d/cirrus.yml > @@ -15,7 +15,7 @@ > stage: build > image: registry.gitlab.com/libvirt/libvirt-ci/cirrus-run:master > needs: [] > - timeout: 80m > + timeout: 100m > allow_failure: true > script: > - source .gitlab-ci.d/cirrus/$NAME.vars IIUC, we need to put a 'timeout_in' setting someone in .gitlab-ci.d/cirrus/build.yml instead, to override Cirrus 60 minute limit: https://cirrus-ci.org/faq/#instance-timed-out 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 :|