From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Patchwork FATE Errors
Date: Thu, 20 Jan 2022 22:22:04 +0100
Message-ID: <AM7PR03MB66604E79DC351A2F3ED213378F5A9@AM7PR03MB6660.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <DM8P223MB0365A3D5457EF2916355D149BA5A9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
Soft Works:
>
> andriy/make_fate_ppc
>
> => Does it possibly need 'make fate-rsync'?
>
No. The test does not rely on need samples; and the other test that uses
this sample works fine. Some time ago, someone else wrote FATE tests for
AVDOVIDecoderConfigurationRecord in Matroska
(https://patchwork.ffmpeg.org/project/ffmpeg/patch/20220101165153.440729-6-tcChlisop0@gmail.com/).
These were faulty and one of them relied on a sample that has apparently
never been uploaded (but this test is actually redundant with the other
test), so I investigated and saw that the test (presumably
unintentially) reencoded audio, so I switched it to a pure copy test and
applied it, believing that codec-copy tests could not possibly for some
arches. That was a mistake and I am deeply sorry for this mess.
Andriy said he would send me the diff etc. to investigate. Right now I
have no real clue what is wrong (the video is 10bit and so the video
pixel format is yuv420p10le here, but that is not part of the output
file at all).
- Andreas
_______________________________________________
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:[~2022-01-20 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 21:03 Soft Works
2022-01-20 21:22 ` Andreas Rheinhardt [this message]
2022-01-20 22:12 ` Soft Works
2022-01-20 22:37 ` Andreas Rheinhardt
2022-01-20 22:59 ` Soft Works
2022-01-21 1:31 ` Andreas Rheinhardt
2022-01-21 1:44 ` Soft Works
2022-01-21 4:24 ` Andriy Gelman
2022-01-21 4:52 ` Soft Works
2022-01-21 5:11 ` Soft Works
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=AM7PR03MB66604E79DC351A2F3ED213378F5A9@AM7PR03MB6660.eurprd03.prod.outlook.com \
--to=andreas.rheinhardt@outlook.com \
--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