\input texinfo @c -*- texinfo -*-
-@settitle FATE Automated Testing Environment
+@settitle FFmpeg Automated Testing Environment
@titlepage
-@center @titlefont{FATE Automated Testing Environment}
+@center @titlefont{FFmpeg Automated Testing Environment}
@end titlepage
@node Top
@chapter Submitting the results to the FFmpeg result aggregation server
To submit your results to the server you should run fate through the
-shell script tests/fate.sh from the FFmpeg sources. This script needs
+shell script @file{tests/fate.sh} from the FFmpeg sources. This script needs
to be invoked with a configuration file as its first argument.
@example
@item version
@end itemize
- When you have everything working properly you can create an SSH key and
-send its public part to the FATE server administrator.
+ When you have everything working properly you can create an SSH key pair
+and send the public key to the FATE server administrator who can be contacted
+at the email address @email{fate-admin@@ffmpeg.org}.
Configure your SSH client to use public key authentication with that key
when connecting to the FATE server. Also do not forget to check the identity
b1:31:c8:79:3f:04:1d:f8:f2:23:26:5a:fd:55:fa:92
+ If you have problems connecting to the FATE server, it may help to try out
+the @command{ssh} command with one or more @option{-v} options. You should
+get detailed output concerning your SSH configuration and the authentication
+process.
+
The only thing left is to automate the execution of the fate.sh script and
the synchronisation of the samples directory.
@item THREADS
Specify how many threads to use while running regression tests, it is
quite useful to detect thread-related regressions.
+@item THREAD_TYPE
+ Specify which threading strategy test, either @var{slice} or @var{frame},
+ by default @var{slice+frame}
@item CPUFLAGS
Specify CPU flags.
@item TARGET_EXEC
through @command{ssh}.
@end table
-Example:
+@section Examples
+
@example
make V=1 SAMPLES=/var/fate/samples THREADS=2 CPUFLAGS=mmx fate
@end example