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-requ...@ffmpeg.org with subject "unsubscribe".
