> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Paul B Mahol
> Sent: Saturday, May 28, 2022 10:50 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] FATE Errors
>
> On Sat, May 28, 2022 at 1
t; Paul B Mahol
> > > > Sent: Saturday, May 28, 2022 10:04 AM
> > > > To: FFmpeg development discussions and patches > > > de...@ffmpeg.org>
> > > > Subject: Re: [FFmpeg-devel] FATE Errors
> > > >
> > > > On Sat, May 28, 2022 at 9:47 AM
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Paul B Mahol
> Sent: Saturday, May 28, 2022 10:33 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] FATE Errors
>
> On Sat, May 28, 2022 at 1
gt; Paul B Mahol
> > > > Sent: Saturday, May 28, 2022 9:35 AM
> > > > To: FFmpeg development discussions and patches > > > de...@ffmpeg.org>
> > > > Subject: Re: [FFmpeg-devel] FATE Errors
> > > >
> > > > On Sat, May 28, 2022 at 9:26 AM
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Paul B Mahol
> Sent: Saturday, May 28, 2022 10:04 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] FATE Errors
>
> On Sat, May 28, 2022 at
On Sat, May 28, 2022 at 9:47 AM Soft Works wrote:
>
>
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> > Paul B Mahol
> > Sent: Saturday, May 28, 2022 9:35 AM
> > To: FFmpeg development discussions and patches > de...@ffmpeg.org>
&
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Paul B Mahol
> Sent: Saturday, May 28, 2022 9:35 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] FATE Errors
>
> On Sat, May 28, 2022 at
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 > de...@ffmpeg.org>
&
> -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 de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] FATE Errors
>
> On Fri, May 27, 2022 at 1
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: [FFm
> -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,
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/v
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> James Almer
> Sent: Saturday, April 30, 2022 9:33 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] FATE Errors
>
>
>
> On 4/30/2022 4:31 PM, Felix LeClair wrote:
> >
> >
On 4/30/2022 4:31 PM, Felix LeClair wrote:
On Apr 30, 2022, at 15:25, Soft Works wrote:
-Original Message-
From: ffmpeg-devel On Behalf Of
Felix LeClair
Sent: Saturday, April 30, 2022 9:22 PM
To: FFmpeg development discussions and patches
Subject: Re: [FFmpeg-devel] FATE
> On Apr 30, 2022, at 15:25, Soft Works wrote:
>
>
>
>> -Original Message-
>> From: ffmpeg-devel On Behalf Of
>> Felix LeClair
>> Sent: Saturday, April 30, 2022 9:22 PM
>> To: FFmpeg development discussions and patches > de...@ffmpeg.or
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Felix LeClair
> Sent: Saturday, April 30, 2022 9:22 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] FATE Errors
>
> Both times I’ve encountered
; From: ffmpeg-devel On Behalf Of
>> James Almer
>> Sent: Saturday, April 30, 2022 9:10 PM
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: Re: [FFmpeg-devel] FATE Errors
>>
>>
>>
>>> On 4/30/2022 4:06 PM, Andreas Rheinhardt wrote:
>>> Sof
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> James Almer
> Sent: Saturday, April 30, 2022 9:10 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] FATE Errors
>
>
>
> On 4/30/2022 4:06 PM, Andreas Rheinhardt wrote:
> > So
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Andreas Rheinhardt
> Sent: Saturday, April 30, 2022 9:07 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] FATE Errors
>
> Soft Works:
> > Hi,
> >
> > is it a known issue
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.3304240
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Felix LeClair
> Sent: Saturday, April 30, 2022 9:01 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] FATE Errors
>
> I’ve been getting the same lo
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 +
> +++ tests/data/fate/vsynt
I’ve been getting the same locally, assumed an issue had already been opened.
-Fclc
> On Apr 30, 2022, at 14:54, Soft Works wrote:
>
> 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 buil
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 +
+++ tests/data/fate/vsynth2-mpeg2-422 2022-04-30 14:38:41
24 matches
Mail list logo
