On 2024-12-04 16:07 +0200, Martin Storsjö wrote:
> On Sun, 1 Dec 2024, Alexander Strasser via ffmpeg-devel wrote:
[...]
> >
> > Would it be better to use the same description as int fate.texi ?
>
> Sure, I can add that extra parenthesis.
Thanks.
[...]
> > > +fate-clear-results:
> > > + @rm -f t
On Sun, 1 Dec 2024, Alexander Strasser via ffmpeg-devel wrote:
Looks good and useful to me.
Thanks!
Just a few ideas follow:
diff --git a/doc/build_system.txt b/doc/build_system.txt
index 0b1b0c2054..91c7a5e9af 100644
--- a/doc/build_system.txt
+++ b/doc/build_system.txt
@@ -30,6 +30,12 @@
Hi Martin!
On 2024-11-07 11:36 +0200, Martin Storsjö wrote:
> If running tests with "make -j fate", the execution will stop
> after the first failing test. To get an overview of the whole
> test suite, one rather would run "make -k -j fate", which then
> again buries the results about what tests a
On Sun, 10 Nov 2024, Michael Niedermayer wrote:
On Thu, Nov 07, 2024 at 11:36:24AM +0200, Martin Storsjö wrote:
If running tests with "make -j fate", the execution will stop
after the first failing test. To get an overview of the whole
test suite, one rather would run "make -k -j fate", which t
On Thu, Nov 07, 2024 at 11:36:24AM +0200, Martin Storsjö wrote:
> If running tests with "make -j fate", the execution will stop
> after the first failing test. To get an overview of the whole
> test suite, one rather would run "make -k -j fate", which then
> again buries the results about what test
