From: Ronan Waide <waider@waider.ie>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] retriggering patchwork for failed fate tests?
Date: Sun, 2 Mar 2025 08:31:35 +0000
Message-ID: <44C98277-BCB9-4AEA-AF0F-185BF1EA4BB8@waider.ie> (raw)
hi folks,
I submitted a patch yesterday which seems to have failed automated `make fate` tests in a place unrelated to the patch (https://patchwork.ffmpeg.org/check/114511/, https://patchwork.ffmpeg.org/check/114513/). I saw a few other patches also failing in this same way - it looks like some libavcodec/tests files contain deprecated usages. I've since seen other patches submitted without tripping over this, so I'm not sure if the failures were triggered specifically by touching files in libavcodec, or if this was an unrelated failure that's since been fixed. `make fate` runs fine on my laptop, but I'm on apple silicon and the failing builds are x86/loongarch64.
What is the correct etiquette here? It seems like my patch may not be at fault, so I could just submit a v5 and see what happens, but that feels like potentially wasting time if it's just going to hit the same problem.
Cheers,
Waider.
--
Ronan Waide
waider@waider.ie
_______________________________________________
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 reply other threads:[~2025-03-02 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 8:31 Ronan Waide [this message]
2025-03-02 10:32 ` Frank Plowman
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=44C98277-BCB9-4AEA-AF0F-185BF1EA4BB8@waider.ie \
--to=waider@waider.ie \
--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