[FFmpeg-devel] releases and stuff
Tue Feb 10 16:22:03 CET 2009
On Tue, Feb 10, 2009 at 04:10:06PM +0100, Benjamin Larsson wrote:
> Diego Biurrun wrote:
> > On Tue, Feb 10, 2009 at 03:56:47PM +0100, Diego Biurrun wrote:
> >> On Tue, Feb 10, 2009 at 01:17:07PM +0100, Dominik 'Rathann' Mierzejewski wrote:
> >>> On Tuesday, 10 February 2009 at 00:32, Carl Eugen Hoyos wrote:
> >>>> Roman V. Shaposhnik <rvs <at> sun.com> writes:
> >>>>> -4435d87463cd6c5407bd88cca241ca56 *./tests/data/a-wmav1.asf
> >>>>> +6f7f3116b801ea641ce14f827de05cce *./tests/data/a-wmav1.asf
> >>>> I remember posting an incredibly beautiful patch to fix it, fortunately I can't
> >>>> find it now;-)
> >>> This?
> >>> Date: Sat, 22 Nov 2008 13:42:11 +0100
> >>> Subject: Re: [FFmpeg-devel] [PATCH] correct make test failure from 15261
> >>> releaseuntil now (15899)
> >> Here is the patch from Carl Eugen, it does indeed fix the WMA regression
> >> tests on PPC. Is this acceptable? Acceptable minus the commented-out
> >> code I mean.
> I strongly object. Doing regressions tests on float code is bound to
<evil mode on>
your objection is noted, and once we have 5 of such checks its time to
rethink but currently this is nice and simple _if_ it works
<evil mode off>
> trigger these things. Instead we should either rely on some SSE metric
<diplomatic mode on>
dear sir, we understand that people can have a memory like a sieve and
it is my pleasure to remind you that asf files are not made of raw floats
that one can compare
<sarcastic mode colission detected assert failure
> or add more valid checksums.
<failure to disable sarcastic mode, lock file found>
because everyone has a ppc and x86 so he can update both when they change?
> Riddling the code with ifdefs just to
> satisfy a misused test system is plain stupid.
something is stu<process killed by admin>
PS: i hope you take my reply not too serious, its a joke and i couldnt
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Frequently ignored awnser#1 FFmpeg bugs should be sent to our bugtracker. User
questions about the command line tools should be sent to the ffmpeg-user ML.
And questions about how to use libav* should be sent to the libav-user ML.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
More information about the ffmpeg-devel