On Wed, Aug 20, 2014 at 11:05:05AM +0200, Peter B. wrote:
On 08/19/2014 12:45 PM, Clément Bœsch wrote:
See:
http://fate.ffmpeg.org/
http://coverage.ffmpeg.org/
The 2nd link to coverage (which should show the LCOV output, I guess)
seems to be broken:
I get a 404 Not Found :(
Sorry
Hi,
On Tue, Aug 19, 2014 at 10:50:31AM +0200, Ondřej Surý wrote:
[...]
From the security viewpoint, I would be also interested if ffmpeg
has tests and what is current code coverage. That could help avoiding
regressions when doing security updates.
1. There are also other tools: llvm/clang
On Sun, Aug 17, 2014 at 09:14:47PM +0200, Luca Barbato wrote:
[...]
Ive asked [1][2] back then what policy in place was broken
- you tried to commit code that was blatantly below the already lax
quality requirements (e.g. it contained tabs, it was (and still is) hard
to read, it contains
3 matches
Mail list logo