From: mkver via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: mkver <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PR] .forgejo/workflows: Test hardcoded tables (PR #21710)
Date: Tue, 10 Feb 2026 10:53:08 -0000
Message-ID: <177072078942.25.15779585879098037775@4457048688e7> (raw)
PR #21710 opened by mkver
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21710
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21710.patch
Should detect breakages like the one caused by commit
d8ffec5bf9a2803f55cc0822a97b7815f24bee83
(fixed in 1d47ae65bf6df91246cbe25c997b25947f7a4d1d).
>From 2459bc193fc11ecac1cecab0eab5414198d957eb Mon Sep 17 00:00:00 2001
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
Date: Tue, 10 Feb 2026 11:50:50 +0100
Subject: [PATCH] .forgejo/workflows: Test hardcoded tables
Should detect breakages like the one caused by commit
d8ffec5bf9a2803f55cc0822a97b7815f24bee83
(fixed in 1d47ae65bf6df91246cbe25c997b25947f7a4d1d).
Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
---
.forgejo/workflows/test.yml | 1 +
1 file changed, 1 insertion(+)
diff --git a/.forgejo/workflows/test.yml b/.forgejo/workflows/test.yml
index a9c9978e53..633330ab74 100644
--- a/.forgejo/workflows/test.yml
+++ b/.forgejo/workflows/test.yml
@@ -82,6 +82,7 @@ jobs:
--extra-cflags="$FF_CFLAGS" --extra-cxxflags="$FF_CXXFLAGS" \
--extra-libs="$FF_LIBS" --extra-ldflags="$FF_LDFLAGS" --extra-ldexeflags="$FF_LDEXEFLAGS" \
--enable-memory-poisoning --assert-level=2 --target-exec="${{ matrix.target_exec }}" \
+ --enable-hardcoded-tables \
|| CFGRES=$?
cat ffbuild/config.log
exit ${CFGRES:-0}
--
2.52.0
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2026-02-10 10:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=177072078942.25.15779585879098037775@4457048688e7 \
--to=ffmpeg-devel@ffmpeg.org \
--cc=code@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