From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FATE Errors
Date: Fri, 27 May 2022 21:10:49 +0000
Message-ID: <DM8P223MB03658F1895956A8DC63CC5B9BAD89@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <AS8PR01MB794426EB1DD60FDCB2198DF68FFF9@AS8PR01MB7944.eurprd01.prod.exchangelabs.com>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Andreas Rheinhardt
> Sent: Saturday, April 30, 2022 10:02 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] FATE Errors
>
> James Almer:
> >
> >
> > On 4/30/2022 4:06 PM, Andreas Rheinhardt wrote:
> >> Soft Works:
> >>> Hi,
> >>>
> >>> is it a known issue that the current head of the master branch
> has
> >>> FATE errors?
> >>>
> >>> I get the same locally as well as on the automated GitHub build.
> >>> One is this:
> >>>
> >>> --- ./tests/ref/vsynth/vsynth2-mpeg2-422 2022-04-30
> >>> 14:23:44.330424058 +0000
> >>> +++ tests/data/fate/vsynth2-mpeg2-422 2022-04-30
> 14:38:41.071678201
> >>> +0000
> >>> @@ -1,4 +1,4 @@
> >>> -b2fa9b73c3547191ecc01b8163abd4e5
> >>> *tests/data/fate/vsynth2-mpeg2-422.mpeg2video
> >>> -379164 tests/data/fate/vsynth2-mpeg2-422.mpeg2video
> >>> -704f6a96f93c2409219bd48b74169041
> >>> *tests/data/fate/vsynth2-mpeg2-422.out.rawvideo
> >>> -stddev: 4.17 PSNR: 35.73 MAXDIFF: 70 bytes: 7603200/ 7603200
> >>> +8f6d565723ccf879ab2b5aa910b7ce21
> >>> *tests/data/fate/vsynth2-mpeg2-422.mpeg2video
> >>> +380544 tests/data/fate/vsynth2-mpeg2-422.mpeg2video
> >>> +0797fddea4835687dedddebbbe98fa8f
> >>> *tests/data/fate/vsynth2-mpeg2-422.out.rawvideo
> >>> +stddev: 4.16 PSNR: 35.73 MAXDIFF: 75 bytes: 7603200/ 7603200
> >>> Test vsynth2-mpeg2-422 failed. Look at
> >>> tests/data/fate/vsynth2-mpeg2-422.err for details.
> >>> make: *** [tests/Makefile:277: fate-vsynth2-mpeg2-422] Error 1
> >>>
> >>>
> >>> Is anybody seeing the same?
> >>>
> >>> Thanks,
> >>> sw
> >>
> >> http://fate.ffmpeg.org/ doesn't show recent regressions and FATE
> is fine
> >> for me locally. I recently made changes to FATE (namely the test
> >> requirements, vcodec.mak (where the vsynth-tests reside) among the
> files
> >> affected), so I am interested in whether the failing tests are
> >> concentrated on the files recently changed by me (it would
> obviously not
> >> haved pushed them if I knew them to cause issues; also patchwork
> was
> >> fine).
> >> Are these issues reproducible? Can you bisect them?
> >>
> >> - Andreas
> >
> > This may be the alignment issue introduced in lavfi in
> >
> https://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=17a59a634c39b00
> a680c6ebbaea58db95594d13d
> > assuming it was not fixed.
> > I think it only affected targets where av_cpu_max_align() returned
> 64.
>
> You are completely right: Just making av_cpu_max_align return 64
> allows
> to reproduce the issue. And it has nothing to do with my recent FATE
> patches (545e87f49dc9fa5b880e330fc4e1854df68cc0f1 would be the only
> contender for changes).
>
I found that the FATE errors can be avoided by using
./configure --disable-avx512
Yet, I hope it will be fixed at some time..
softworkz
_______________________________________________
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-05-27 21:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 18:54 Soft Works
2022-04-30 19:01 ` Felix LeClair
2022-04-30 19:07 ` Soft Works
2022-04-30 19:06 ` Andreas Rheinhardt
2022-04-30 19:09 ` James Almer
2022-04-30 19:19 ` Soft Works
2022-04-30 19:22 ` Felix LeClair
2022-04-30 19:25 ` Soft Works
2022-04-30 19:31 ` Felix LeClair
2022-04-30 19:33 ` James Almer
2022-04-30 19:39 ` Soft Works
2022-04-30 20:02 ` Andreas Rheinhardt
2022-05-27 21:10 ` Soft Works [this message]
2022-05-28 7:25 ` Paul B Mahol
2022-05-28 7:26 ` Soft Works
2022-05-28 7:34 ` Paul B Mahol
2022-05-28 7:47 ` Soft Works
2022-05-28 8:04 ` Paul B Mahol
2022-05-28 8:12 ` Soft Works
2022-05-28 8:33 ` Paul B Mahol
2022-05-28 8:41 ` Soft Works
2022-05-28 8:50 ` Paul B Mahol
2022-05-28 8:57 ` Soft Works
2022-04-30 19:12 ` 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=DM8P223MB03658F1895956A8DC63CC5B9BAD89@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz@hotmail.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