From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 7B87242B88 for ; Sat, 28 May 2022 07:32:02 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 78F8868B58D; Sat, 28 May 2022 10:31:59 +0300 (EEST) Received: from mail-yb1-f182.google.com (mail-yb1-f182.google.com [209.85.219.182]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id C37F968B1CE for ; Sat, 28 May 2022 10:31:52 +0300 (EEST) Received: by mail-yb1-f182.google.com with SMTP id o80so11361334ybg.1 for ; Sat, 28 May 2022 00:31:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=f6ueQJKqgl9h38o4AjU3XUlO3X7tTosRrUcYhxAO0fk=; b=GToaFxF/ARMLrQouJ0lhfLylsN0lCS5cb7Say4KiT0TS1WouW6EDLHwV/9ivdFaE4F k432bf1GVCgjaqxnQDGeulsqmroRQfVuBR4qClSIpH/E3bRU4sDYUPlsSSedv3RrhWeN yImbH5nObYKXnkEDSyUdWXXTlc5undIVFU9sKtURhEdKglhxEhkW6UDBOnqpYHV6Zlcd gjuEMOi/q0u/9cb07X+YJSDNLTtw1XNeqJ+YOP4mtlTa1z7m9bpoHeo26dF9gcYHz0H/ ci7puZkwpeHs9sjj2TpJmqgupRSDTOjZa8444h/uw5NZFPQGo+rpIGe4pGgONh2E0bVS ZYuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=f6ueQJKqgl9h38o4AjU3XUlO3X7tTosRrUcYhxAO0fk=; b=izrxTGza1z4zXOxmr8i3QjyqeGs+iD4xX5l9hA2Ryplk1j3d/okskc4mITbPtQCNhK /TOZoJZucSSZ/ydaBttysXj84ajX4ruwMw4AAP0oGZHLi6OiSc9qkXGxeBgR3nOsKv2Q zJD+lF9XOA92kMZxHGcNmbywCQpajTAIuDbDemlRpqsP8ZMYIIFWqbxSArCYKZRXdJte Yj+Ax8a9GJPiPJYWZv3SWZUs9OwsWy3+E7L2mLP183TRObBW7++gId0SnLMmb5NeEzwC ydLaLDS+I1xF15cyzCS6FhBk8XaxFZZ5XNH+RVLEoqOrpNF2VcC/yqwlXkoRh3bXpgIM YbTg== X-Gm-Message-State: AOAM530MNhL/yr5Z7vhDaMpNml2D4/kwaW/ILtwC8z5b7EyZ+RjQDI+x 1dTpojE0fxUXcErjg6EgCteG53HO+QaC+WxmI5GRFBED X-Google-Smtp-Source: ABdhPJxRe0n7UrkSY2e6eIoUK8M/8SLz6JiuG1mklm2FomkhwGtGitsjj8fNjs/pgghTYvTG7U1qoJm7uFfYAb2kWJQ= X-Received: by 2002:a05:6902:108b:b0:652:ea9:980c with SMTP id v11-20020a056902108b00b006520ea9980cmr21318720ybu.250.1653723111580; Sat, 28 May 2022 00:31:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Paul B Mahol Date: Sat, 28 May 2022 09:34:39 +0200 Message-ID: To: FFmpeg development discussions and patches X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [FFmpeg-devel] FATE Errors X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On Sat, May 28, 2022 at 9:26 AM Soft Works wrote: > > > > -----Original Message----- > > From: ffmpeg-devel On Behalf Of > > Paul B Mahol > > Sent: Saturday, May 28, 2022 9:26 AM > > To: FFmpeg development discussions and patches > devel@ffmpeg.org> > > Subject: Re: [FFmpeg-devel] FATE Errors > > > > On Fri, May 27, 2022 at 11:11 PM Soft Works > > wrote: > > > > > > > > > > > > -----Original Message----- > > > > From: ffmpeg-devel 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.. > > > > > > > I hope you will post a fix for it soon. > > That depends on whether we want alignment values > 32bit..? > Nope, its about mpeg video encoder in lavc that does funny things from old days when linesize alignment was hardcoded. > _______________________________________________ > 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". > _______________________________________________ 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".