> -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> 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 Apr 30, 2022, at 15:25, Soft Works <softwo...@hotmail.com> > wrote: > >> > >> > >> > >>> -----Original Message----- > >>> From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of > >>> Felix LeClair > >>> Sent: Saturday, April 30, 2022 9:22 PM > >>> To: FFmpeg development discussions and patches <ffmpeg- > >>> de...@ffmpeg.org> > >>> Subject: Re: [FFmpeg-devel] FATE Errors > >>> > >>> Both times I’ve encountered were on PopOS (think Debian/Ubuntu > meets > >>> arch like timing release) > >> > >> VM or bare metal installation? > >> > >> PS: The people here don't like top-posting > >> > >> Thanks, > >> 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-requ...@ffmpeg.org with subject "unsubscribe". > > > > It’s a bare metal installation, intel x86 12th gen, ecores > disabled, AVX512 enabled (instructions include ice lake + FP16), > kernel 5.18rc3. > > Then i was right. AVX512 support means av_cpu_max_align() returns 64.
Makes sense. Mine is 11 gen and I looked at the CI build history (https://dev.azure.com/githubsync/ffmpeg/_build?definitionId=9&_a=summary) which shows some runs have passed and some failed during the recent past - probably depending on the host machine type that gets the job. 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-requ...@ffmpeg.org with subject "unsubscribe".
