From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 552E44BA87 for ; Tue, 22 Jul 2025 18:07:58 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 529DC68D2DC; Tue, 22 Jul 2025 21:07:54 +0300 (EEST) Received: from btbn.de (btbn.de [144.76.60.213]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 5CC0968C183 for ; Tue, 22 Jul 2025 21:07:48 +0300 (EEST) Received: from [authenticated] by btbn.de (Postfix) with ESMTPSA id C7FFD27FD33C3 for ; Tue, 22 Jul 2025 20:07:47 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rothenpieler.org; s=mail; t=1753207667; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=gu1pIIZ5tfGKBZPlH4vhheSrN5ZcCKvW7tFMC2KWb8M=; b=L4uH+5WMhvbAAQRV6HndzGFEVEgxEHnCr7MnByYgzFlJPmgm2dKdJOSUC7Luk9iWskqevl m1fTuDDpiQDC4uqZFQI4d1qtIdBNbWY+ZkcTha7sIufLbDV2b0qLXq6jI7y1BpxvBRTLcA BErAEDDsiywol0BQjodIa+7rw9SyXAb+PbCmgQUrersKRjnnybpktZbOIToxxK+V/D4ML3 uHQ6ShgGRFKM86FVgyrSOXK501WjqkSU32AhXGnSSuzSRZGu3Leml3d+35u7ikDzL9tdGY lxTCZttaTILgmbAVlmUlIISM09BFce+yNG7a83K8JnFqsGLkRW5XOrG1pbdPdQ== Message-ID: <6573a0e5-2e56-484c-97a2-cd318249c5cc@rothenpieler.org> Date: Tue, 22 Jul 2025 20:07:47 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: ffmpeg-devel@ffmpeg.org References: <20250721163710.888-1-timo@rothenpieler.org> <20250721221735.GB29660@pb2> <20250722170908.GF29660@pb2> Content-Language: en-US From: Timo Rothenpieler In-Reply-To: <20250722170908.GF29660@pb2> Subject: Re: [FFmpeg-devel] [PATCH] forgejo/workflows: add initial rudimentary CI X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On 7/22/2025 7:09 PM, Michael Niedermayer wrote: > Hi > > On Tue, Jul 22, 2025 at 01:00:49AM +0200, Timo Rothenpieler wrote: >> On 7/22/2025 12:17 AM, Michael Niedermayer wrote: >>> On Mon, Jul 21, 2025 at 06:37:06PM +0200, Timo Rothenpieler wrote: > [...] >>> --enable-version3 >>> --cc='ccache gcc' (or clang) >> >> I don't fully trust ccache to not cause spurious issues. > > locally i think ive never seen an issue and i use it 100% of teh time > for all builds. > > in fate clients, i have seen cases where ccache needed to be cleared > I dont want to guess the cause as its just a guess, but clients > run out of disk space, they run out of memory which doesnt happen > to me locally nearly that often > > >> Gentoo stopped accepting bug reports if ccache was involved and it wasn't >> reproduced without it. > >> The builds are speedy enough that a full build each time doesn't seem too >> horrible. > > Being able to tell the developer code is ok/not ok quicker can be valuable > but sure, if you prefer having it disabled for now > >> >> I'd rather just add more runners if we ever run into capacity problems, >> which I honestly don't see happening anytime soon. >> >>> --assert-level=2 >>> --tempprefix=somebasepaththatcanbeusedforcreatingtemporaryfiles >> >> If I understand this right, all it does is use a fixed prefix in /tmp >> instead of just calling mktemp? >> I don't immediately see the benefit of that, speed wise. > > its for ccache. Because without that you have random temporary files > and so they are not cached. > > my configure here takes 6sec (with --tempprefix and ccache and lots of --enables) > without tempprefix its 10sec If we do run into capacity problems, we can always look into that. I've applied this initial rudimentary version for now. It's just a very baseline CI setup for now anyway, and will be expanded on. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".