* [FFmpeg-devel] [FFmpeg-devel][QUESTION] Add new sample to fate-suite via forgejo
@ 2025-09-18 9:25 Zhao Zhili via ffmpeg-devel
2025-09-18 14:27 ` [FFmpeg-devel] " Timo Rothenpieler via ffmpeg-devel
0 siblings, 1 reply; 2+ messages in thread
From: Zhao Zhili via ffmpeg-devel @ 2025-09-18 9:25 UTC (permalink / raw)
To: FFmpeg development discussions and patches; +Cc: Timo Rothenpieler, Zhao Zhili
Current situation:
1. A patch depends on new sample in fate-suit will fail CI
2. New sample needs to upload to fate-suit server manually
Question: Is it possible to hook sample uploading request to forgejo?
A simple idea is:
1. Setup a git repo with git-lfs support for fate-suit.
2. Add new sample via sending PR to this fate-suit repo.
3. Add cross link and rerun CI manually in FFmpeg repo’s PR after fate-suit’s PR merged.
Maybe there are more simpler methods to do that.
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
^ permalink raw reply [flat|nested] 2+ messages in thread
* [FFmpeg-devel] Re: [FFmpeg-devel][QUESTION] Add new sample to fate-suite via forgejo
2025-09-18 9:25 [FFmpeg-devel] [FFmpeg-devel][QUESTION] Add new sample to fate-suite via forgejo Zhao Zhili via ffmpeg-devel
@ 2025-09-18 14:27 ` Timo Rothenpieler via ffmpeg-devel
0 siblings, 0 replies; 2+ messages in thread
From: Timo Rothenpieler via ffmpeg-devel @ 2025-09-18 14:27 UTC (permalink / raw)
To: Zhao Zhili, FFmpeg development discussions and patches; +Cc: Timo Rothenpieler
[-- Attachment #1.1: Type: text/plain, Size: 940 bytes --]
On 9/18/2025 11:25 AM, Zhao Zhili wrote:
> Current situation:
> 1. A patch depends on new sample in fate-suit will fail CI
Just temporarily manually download it in the workflow, and before the PR
gets merged, have the sample be uploaded to the fate-suite and remove
the manual download.
That's how it's been handled so far.
> 2. New sample needs to upload to fate-suit server manually
>
> Question: Is it possible to hook sample uploading request to forgejo?
A PR that needs a new sample pretty much is that imo.
> A simple idea is:
> 1. Setup a git repo with git-lfs support for fate-suit.
> 2. Add new sample via sending PR to this fate-suit repo.
> 3. Add cross link and rerun CI manually in FFmpeg repo’s PR after fate-suit’s PR merged.
>
> Maybe there are more simpler methods to do that.
So far all methods I could think of were more or less the same level of
effort than the current approach.
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4742 bytes --]
[-- Attachment #2: Type: text/plain, Size: 163 bytes --]
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-09-18 14:28 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-09-18 9:25 [FFmpeg-devel] [FFmpeg-devel][QUESTION] Add new sample to fate-suite via forgejo Zhao Zhili via ffmpeg-devel
2025-09-18 14:27 ` [FFmpeg-devel] " Timo Rothenpieler via ffmpeg-devel
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