[FFmpeg-devel] FFserver refactor and bugfixes
klaxa1337 at googlemail.com
Fri Jun 1 22:59:37 EEST 2018
On Fri, Jun 1, 2018 at 9:24 PM, Michael Niedermayer
<michael at niedermayer.cc> wrote:
> On Fri, Jun 01, 2018 at 12:23:53AM +0200, Stephan Holljes wrote:
>> This patch series got a bit larger than I hoped, but there were quite
>> some more things to fix. Also a number of these commits are of cosmetic
> btw, what are the plans for selftests ? (similar to fate) for ffserver
That's a good question, I haven't thought too deeply on that. So far
my testing has been rather basic. I simply check if the stream is
playable and I test server-load with a lot of wget processes.
Having a set of standard tests to find regressions is a very good
idea, but I'm not sure how to properly implement it. Given the nature
of multi-threaded programs it's probably impossible to have every test
execute exactly the same, but each run should have the same effects.
Looking at how fate does testing will probably a good starting point.
Thanks for the obvious suggestion I didn't think about!
> Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
> Breaking DRM is a little like attempting to break through a door even
> though the window is wide open and the only thing in the house is a bunch
> of things you dont want and which you would get tomorrow for free anyway
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
More information about the ffmpeg-devel