Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] FATE Errors
Date: Sat, 30 Apr 2022 21:06:42 +0200
Message-ID: <AS8PR01MB79442E45CC681125817FF2D58FFF9@AS8PR01MB7944.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <DM8P223MB0365E695970BBD2E9B7FEDE3BAFF9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>

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
_______________________________________________
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".

  parent reply	other threads:[~2022-04-30 19:06 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 [this message]
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
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=AS8PR01MB79442E45CC681125817FF2D58FFF9@AS8PR01MB7944.eurprd01.prod.exchangelabs.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