From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] forgejo/workflows: add initial rudimentary CI
Date: Tue, 22 Jul 2025 19:09:08 +0200
Message-ID: <20250722170908.GF29660@pb2> (raw)
In-Reply-To: <a82d8b15-3294-45c0-b0db-bd8cca9ec62e@rothenpieler.org>
[-- Attachment #1.1: Type: text/plain, Size: 1811 bytes --]
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
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
While the State exists there can be no freedom; when there is freedom there
will be no State. -- Vladimir Lenin
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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".
next prev parent reply other threads:[~2025-07-22 17:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 16:37 Timo Rothenpieler
2025-07-21 17:02 ` Leo Izen
2025-07-21 17:44 ` Timo Rothenpieler
2025-07-21 19:24 ` Timo Rothenpieler
2025-07-21 22:17 ` Michael Niedermayer
2025-07-21 22:40 ` Scott Theisen
2025-07-21 23:27 ` Kacper Michajlow
2025-07-21 23:00 ` Timo Rothenpieler
2025-07-22 17:09 ` Michael Niedermayer [this message]
2025-07-22 18:07 ` Timo Rothenpieler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250722170908.GF29660@pb2 \
--to=michael@niedermayer.cc \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git