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 D7649EE645E for ; Thu, 12 Sep 2024 08:16:04 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1soezg-00026p-5J; Thu, 12 Sep 2024 04:16:00 -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 1soeze-00020n-FC for qemu-devel@nongnu.org; Thu, 12 Sep 2024 04:15:58 -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 1soezb-0005TS-BH for qemu-devel@nongnu.org; Thu, 12 Sep 2024 04:15:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1726128952; 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=tBTOpSj9XzXopRs7HSMWkd5Cs4lRNHskPcrYAmS58Iw=; b=P2gZm6Nu8DVbTGfGo20OF10+t55PcARJ5+Cs9SSzJ4KzynmlLgBWAMDgp/JJfr1TLSXNwA YtQeci+ra6FIP5bUn7Cxd4VRJpJFBX36s03txwqIpgNtuwEuKW4AW9gl3Oi3ns8s6VMETy T+ycRl0k3WZvsPq0RPhBNT+eQpoPvSw= Received: from mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-113-bOJHhm1ZMyOOIxpTkPzBAg-1; Thu, 12 Sep 2024 04:15:48 -0400 X-MC-Unique: bOJHhm1ZMyOOIxpTkPzBAg-1 Received: from mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id BF16F1945105; Thu, 12 Sep 2024 08:15:47 +0000 (UTC) Received: from redhat.com (unknown [10.42.28.140]) by mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 045E51956086; Thu, 12 Sep 2024 08:15:44 +0000 (UTC) Date: Thu, 12 Sep 2024 09:15:41 +0100 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Thomas Huth Cc: Paolo Bonzini , QEMU Developers , Peter Maydell , Stefan Hajnoczi , Richard Henderson Subject: Re: Gitlab CI caching is not working Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.2.12 (2023-09-09) X-Scanned-By: MIMEDefang 3.0 on 10.30.177.15 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: -21 X-Spam_score: -2.2 X-Spam_bar: -- X-Spam_report: (-2.2 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.144, 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_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=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 Thu, Sep 12, 2024 at 07:38:37AM +0200, Thomas Huth wrote: > > Hi! > > While looking at some recent CI jobs, I noticed that the caching of the > Gitlab-CI jobs is not working at all anymore. In the build jobs, the ccache > saving is not working and causing a complete cache miss of each compile: > > https://gitlab.com/qemu-project/qemu/-/jobs/7802183187#L5328 > > And, maybe more important, in the avocado/functional jobs we don't cache the > assets anymore, causing a re-download of multiple gigabytes each time: > > https://gitlab.com/qemu-project/qemu/-/jobs/7802183251#L29 > > (the du -chs in line 35 is not executed, thus the cache is nonexistent) > > The problem is not new, it's been there for some weeks already, e.g. here's > a run from the last freeze period (when the job was only running avocado > tests): > > https://gitlab.com/qemu-project/qemu/-/jobs/7753544153#L86 > > There is a suspicious message at the beginning of the logs: > > "No URL provided, cache will not be downloaded from shared cache server. > Instead a local version of cache will be extracted." > > ... but since we use throw-away containers for building, I guess there is no > local version of the cache? > > Anyway, the problem only exists for the k8s runners, in my private clone of > the repository that uses shared runners from gitlab, the caching is working > right. Right, by default caches are local to the runner's execution environment. If you want a distributed cache, that has to be turned on in the runner configuration: https://docs.gitlab.com/runner/configuration/autoscale.html#distributed-runners-caching 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 :|