FFmpeg  4.3
Functions | Variables
doc/fate.txt File Reference

Functions

FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg can be set or it has a meaning only while running the regression tests ‘THREADS’ Specify how many threads to use while running regression it is quite useful to detect thread related regressions ‘THREAD_TYPE’ Specify which threading strategy either ‘slice’ or by default ‘slice frame’ ‘CPUFLAGS’ Specify CPU flags ‘TARGET_EXEC’ Specify or override the wrapper used to run the tests The ‘TARGET_EXEC’ option provides a way to run FATE wrapped in ‘qemu user’ or ‘wine’ or on remote targets through ‘ssh’ ‘GEN’ Set to ‘1’ to generate the missing or mismatched references ‘HWACCEL’ Specify which hardware acceleration to use while running regression by default ‘none’ is used ‘KEEP’ Set to ‘1’ to keep temp files generated by fate test (s) when test is successful. Default is ‘0’
 

Variables

FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this website
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of CPU
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source directory
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the test
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your needs
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet used
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell script
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration file
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new samples
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as possible
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each client
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample files
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not replace
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be uploaded
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally hours
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL chmod =Dg+s
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo x
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug rw
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o r
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o w
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg org
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg can be set to
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg can be set or 
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg can be set or it has a meaning only while running the regression tests ‘THREADS’ Specify how many threads to use while running regression tests
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg can be set or it has a meaning only while running the regression tests ‘THREADS’ Specify how many threads to use while running regression it is quite useful to detect thread related regressions ‘THREAD_TYPE’ Specify which threading strategy either ‘slice’ or ‘frame’
 
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg can be set or it has a meaning only while running the regression tests ‘THREADS’ Specify how many threads to use while running regression it is quite useful to detect thread related regressions ‘THREAD_TYPE’ Specify which threading strategy either ‘slice’ or by default ‘slice frame’ ‘CPUFLAGS’ Specify CPU flags ‘TARGET_EXEC’ Specify or override the wrapper used to run the tests The ‘TARGET_EXEC’ option provides a way to run FATE wrapped in ‘valgrind’
 

Function Documentation

◆ test()

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite***************************************** If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg can be set or it has a meaning only while running the regression tests ‘THREADS’ Specify how many threads to use while running regression it is quite useful to detect thread related regressions ‘THREAD_TYPE’ Specify which threading strategy either ‘slice’ or by default ‘slice frame’ ‘CPUFLAGS’ Specify CPU flags ‘TARGET_EXEC’ Specify or override the wrapper used to run the tests The ‘TARGET_EXEC’ option provides a way to run FATE wrapped in ‘qemu user’ or ‘wine’ or on remote targets through ‘ssh’ ‘GEN’ Set to ‘1’ to generate the missing or mismatched references ‘HWACCEL’ Specify which hardware acceleration to use while running regression by default ‘none’ is used ‘KEEP’ Set to ‘1’ to keep temp files generated by fate test ( s  )

Variable Documentation

◆ website

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this website

Definition at line 30 of file fate.txt.

◆ CPU

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of CPU

Definition at line 36 of file fate.txt.

◆ directory

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source directory

Definition at line 72 of file fate.txt.

◆ test

FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg can be set or it has a meaning only while running the regression tests ‘THREADS’ Specify how many threads to use while running regression it is quite useful to detect thread related regressions ‘THREAD_TYPE’ Specify which threading strategy test

◆ needs

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your needs

Definition at line 91 of file fate.txt.

Referenced by mc_block().

◆ used

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet used

◆ script

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell script

Definition at line 95 of file fate.txt.

Referenced by parse_script(), sbg_read_header(), and sbg_read_probe().

◆ file

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration file

◆ samples

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite***************************************** If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new samples
Examples
encode_audio.c.

Definition at line 139 of file fate.txt.

Referenced by aac_decode_er_frame(), aac_decode_frame_int(), aac_encode_frame(), ac3_downmix_5_to_1_symmetric_c(), ac3_downmix_5_to_1_symmetric_c_fixed(), ac3_downmix_5_to_2_symmetric_c(), ac3_downmix_5_to_2_symmetric_c_fixed(), ac3_downmix_c(), ac3_downmix_c_fixed(), ac3_downmix_c_fixed16(), adpcm_analysis(), adpcm_compress_trellis(), adpcm_decode_frame(), adpcm_swf_decode(), adx_decode_frame(), adx_encode_frame(), alac_entropy_coder(), alac_linear_predictor(), amr_wb_encode_frame(), analyze_mono(), aptx_decode_channel(), aptx_decode_frame(), aptx_decode_samples(), aptx_encode_channel(), aptx_encode_frame(), aptx_encode_samples(), aptx_qmf_polyphase_analysis(), aptx_qmf_polyphase_synthesis(), aptx_qmf_tree_analysis(), aptx_qmf_tree_synthesis(), ast_write_trailer(), autoregression(), av_adts_header_parse(), available_samples(), avisynth_read_packet_audio(), avresample_get_out_samples(), butter_filter_stereo_samples(), calc_stereo_peak(), calc_stereo_rms(), cinaudio_decode_frame(), cng_encode_frame(), config_output(), conv(), cook_decode_frame(), copy_input_samples(), decode_frame(), decode_part_stereo(), decode_residuals(), decorr_mono_buffer(), draw_legend(), dv_get_audio_sample_count(), encode_frame(), evrc_decode_frame(), ff_aac_update_ltp(), ff_ac3dsp_downmix(), ff_ac3dsp_downmix_fixed(), ff_dca_core_filter_fixed(), ff_dca_downmix_to_stereo_fixed(), ff_dca_downmix_to_stereo_float(), ff_dca_lbr_flush(), ff_dca_xll_filter_frame(), ff_dsd2pcm_translate(), ff_framequeue_skip_samples(), ff_inlink_check_available_samples(), ff_lpc_calc_coefs(), ff_lpc_calc_ref_coefs(), ff_lpc_calc_ref_coefs_f(), ff_mlp_rematrix_channel(), ff_mpa_synth_filter(), ff_mpadsp_apply_window(), ff_msgsm_decode_block(), ff_samples_to_time_base(), ff_tilt_compensation(), ff_vorbis_floor1_render_list(), fill_in_adpcm_bufer(), filter(), filter_channel(), filter_frame(), filter_frame_fixed(), filter_frame_float(), filter_samples(), filter_ts(), flac_decorrelate_indep_c(), flac_decorrelate_ls_c(), flac_decorrelate_ms_c(), flac_decorrelate_rs_c(), flac_read_header(), floor_encode(), frame_erasure(), frame_list_remove_samples(), g722_encode_trellis(), get_frame_internal(), get_packet_header(), gsm_decode_block(), gsm_decode_frame(), hb_synthesis(), hdcd_analyze(), hdcd_analyze_prepare(), hdcd_envelope(), hdcd_integrate(), hdcd_process(), hdcd_process_stereo(), hdcd_scan(), input_data(), input_data_internal(), isfinite_array(), libAVMemInputPin_ReceiveMultiple(), libcodec2_encode(), libgsm_decode_frame(), libgsm_encode_frame(), libvorbis_encode_frame(), log2mono(), mace_decode_frame(), main(), mix_1_to_2_fltp_flt_c(), mix_2_to_1_s16p_flt_c(), mix_2_to_1_s16p_q8_c(), mix_2_to_6_fltp_flt_c(), mix_6_to_2_fltp_flt_c(), MIX_FUNC_GENERIC(), mov_build_index(), mov_read_custom(), mp_decode_frame(), MPA_encode_frame(), mxf_write_d10_audio_packet(), oggvorbis_decode_frame(), opus_decode_frame(), opus_decode_subpacket(), parse_ch(), parse_frame_data(), parse_x96_frame_data(), parse_x96_subframe_audio(), pcm_bluray_decode_frame(), pcm_decode_frame(), pcm_dvd_decode_samples(), pcm_dvd_encode_frame(), pcm_encode_frame(), postfilter(), postfilter_5k0(), predict(), pulse_write_packet(), r3d_read_reda(), ra144_decode_frame(), ra144_encode_frame(), random_ts(), read_packet(), read_samples_from_audio_fifo(), recurse_mono(), request_frame(), residue_encode(), s302m_encode2_frame(), sample_queue_push(), scan_word(), setup_array(), shift_mono(), sipr_decode_frame(), smka_decode_frame(), spdif_get_offset_and_codec(), spdif_header_aac(), spectral_to_sample(), synth_frame(), synth_lpc(), synth_superframe(), synthesis(), synthesis_filter(), synthfilt_build_sb_samples(), tak_decode_frame(), transform_channel(), truespeech_decode_frame(), tta_decode_frame(), tta_encode_frame(), update_md5_sum(), update_sample_display(), wma_decode_frame(), wma_decode_superframe(), write_element(), write_frame(), ws_snd_decode_frame(), wv_mono(), wv_unpack_mono(), and wv_unpack_stereo().

◆ possible

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite***************************************** If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as possible

Definition at line 140 of file fate.txt.

◆ client

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite***************************************** If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each client
Examples
http_multiclient.c.

Definition at line 140 of file fate.txt.

Referenced by main(), and process_client().

◆ files

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite***************************************** If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample files

Definition at line 142 of file fate.txt.

Referenced by real_seek().

◆ replace

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite***************************************** If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not replace

Definition at line 142 of file fate.txt.

Referenced by activate(), and mm_decode_inter().

◆ uploaded

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite***************************************** If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be uploaded

Definition at line 144 of file fate.txt.

◆ hours

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite***************************************** If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally hours

◆ chmod

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite***************************************** If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL chmod =Dg+s

Definition at line 150 of file fate.txt.

◆ x

FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo x
Examples
encode_video.c, filtering_video.c, muxing.c, and scaling_video.c.

Definition at line 150 of file fate.txt.

Referenced by __align__(), a0(), a1(), a2(), a3(), a64multi_encode_frame(), acolor(), acolor16(), activate(), add_dc(), add_mv_data(), add_rect_clamped_c(), add_residual(), add_yblock(), aic_decode_frame(), alac_entropy_coder(), alias_pix_read_probe(), all_same(), alpha(), alpha_composite(), alpha_inverse_prediction(), alphasum(), amp_test(), amplify_frame(), anaglyph(), anaglyph_ic(), analyze(), ape_decode_value_3860(), ape_decode_value_3900(), ape_decode_value_3990(), APESIGN(), apng_do_inverse_blend(), apply_color_indexing_transform(), apply_color_transform(), apply_delogo(), apply_ir_filter(), apply_loop_filter(), apply_lut(), apply_motion_generic(), apply_obmc(), apply_palette(), apply_predictor_transform(), apply_subtract_green_transform(), aura_decode_frame(), autocorrelate(), av_bswap16(), av_bswap32(), av_bswap64(), av_ceil_log2_c(), av_image_fill_black(), av_lzo1x_decode(), av_popcount64_c(), av_popcount_c(), av_rc4_crypt(), av_read_image_line(), av_read_image_line2(), av_reduce(), av_write_image_line(), av_write_image_line2(), av_x_if_null(), avfilter_graph_dump_to_buf(), avfilter_transform(), avg_c(), avg_no_rnd_vc1_chroma_mc4_c(), avg_no_rnd_vc1_chroma_mc8_c(), avpriv_isfinite(), avpriv_isfinitef(), avpriv_isinf(), avpriv_isinff(), avpriv_isnan(), avpriv_isnanf(), avpriv_mirror(), avpriv_toupper4(), avs_decode_frame(), b0(), b1(), b2(), b3(), b44_uncompress(), b_func(), ball_to_xyz(), barrelsplit_to_xyz(), basic_block_filtering(), bayes_threshold(), bessel(), bessel_filter(), bessel_I_0(), bidirectional_obmc(), bilateral_obmc(), biquad(), bitline2chunky(), bitplanar2chunky(), bitplane_decoding(), bitreduction(), bitswap_32(), blend_frame_partial(), blend_hline(), blend_hline16(), blend_line(), blend_line16(), blend_line_hv(), blend_line_hv16(), blend_pixel(), blend_pixel16(), blend_plane(), blend_slice_packed_rgb(), blend_slice_planar_rgb(), blend_slice_yuv(), block_angle(), block_contrast(), block_matching_multi(), blur(), blur_image(), blur_pixel(), build_abs_diff_mask(), build_basis(), build_diff_map(), build_filter(), build_huffman(), burn_frame16(), burn_frame8(), byte2word48(), byte2word64(), BYTE_VEC(), calc_avgy16(), calc_avgy8(), calc_combed_score(), calc_corr(), calc_diffs(), calc_persp_luts(), calculate_display_rect(), calculate_gaussian_coeffs(), calculate_lanczos_coeffs(), calculate_mode_score(), calculate_skip_errors(), calculate_visual_weight(), capture_screen(), cas_slice16(), cas_slice8(), cb(), cbp_test(), cbrt(), cbrtf(), cbsum(), cdg_tile_block(), cdtoons_render_sprite(), cdxl_decode_ham6(), cdxl_decode_ham8(), celt_autocorr(), celt_cos(), celt_decode_coarse_energy(), celt_fir5(), celt_inner_prod(), celt_pitch_xcorr(), check_checksum(), check_intra_mode(), check_itxfm(), choose_rct_params(), chroma(), chroma16(), cinepak_decode_vectors(), cinepak_encode_end(), cinepak_encode_init(), clean_mean(), clip_interval(), cluster_mvs(), clv_decode_frame(), cmp(), cmp_direct_inline(), cmp_fpel_internal(), cmp_hpel(), cmp_inline(), cmp_internal(), cmp_qpel(), cmp_simple(), cmv_decode_inter(), cmv_motcomp(), cocg_block(), codeblock(), codec37_mv(), color(), color16(), color_correlation(), color_correlation_gbrp(), color_decorrelation(), color_decorrelation_gbrp(), color_graticule(), color_graticule16(), colorlevel_slice_16(), colorlevel_slice_8(), compare(), compare_fields(), complex_divide(), complex_multiply(), compose(), compose2D(), compress_alpha(), compute_default_clut(), compute_histogram16(), compute_histogram8(), compute_mb_distortion(), compute_metric(), compute_safe_ssd_integral_image_c(), compute_unsafe_ssd_integral_image(), config_input(), config_output(), config_video_output(), constant_color(), convert(), convert_frame_partial(), convert_mask_to_strength_mask(), copy_avg_fn(), copy_block(), copy_CTB_to_hv(), copy_frame(), copy_from(), copy_pad(), copy_picture_field(), copy_rectangle(), copy_rectangles(), copyadd_block(), copysign(), copysignl(), correlate(), correlate_slice_buffered(), count_colors(), count_hq_slice(), cover_rect(), cqt_calc(), cr(), create_cel_evals(), create_freq_table(), crossover_setup(), crsub(), cubic_interpolate_func(), dc_test(), dds_decode(), deband_16_c(), deband_16_coupling_c(), deband_8_c(), deband_8_coupling_c(), deblocking_filter_CTB(), debug_mean_error(), decfloat(), decode(), decode_0(), decode_13(), decode_555(), decode_alpha_block(), decode_argb(), decode_argbi(), decode_argx(), decode_argxi(), decode_aybr(), decode_aybri(), decode_block(), decode_block_params(), decode_blocks(), decode_byry(), decode_byryi(), decode_byte_vertical_delta(), decode_byterun(), decode_c82i(), decode_c82p(), decode_ca2i(), decode_ca2p(), decode_ca4i(), decode_ca4p(), decode_cell(), decode_cell_data(), decode_clnpass(), decode_coeffs(), decode_colskip(), decode_decorrelation_matrix(), decode_deep_rle32(), decode_deep_tvdc32(), decode_delta_d(), decode_delta_e(), decode_dlta(), decode_entropy_coded_image(), decode_entropy_image(), decode_frame(), decode_frame_common(), decode_huffman2(), decode_hybrid(), decode_i2_frame(), decode_i_frame(), decode_init(), decode_init_static(), decode_inter(), decode_inter_plane(), decode_intra(), decode_intra4x4_modes(), decode_intra_plane(), decode_line(), decode_long_vertical_delta(), decode_long_vertical_delta2(), decode_mb(), decode_mb_coeffs(), decode_mb_info(), decode_mode(), decode_mvc1(), decode_mvc2(), decode_mvdv(), decode_p_frame(), decode_pixel_in_context(), decode_plane(), decode_q_branch(), decode_raw_intra(), decode_raw_intra_rgb(), decode_refpass(), decode_region(), decode_region_inter(), decode_region_intra(), decode_region_masked(), decode_rgb(), decode_rgb8(), decode_rgb_frame(), decode_rgbi(), decode_rgbn(), decode_rgbx(), decode_rgbxi(), decode_rle(), decode_rowskip(), decode_run_i(), decode_run_p(), decode_runlen(), decode_runlen_rgb(), decode_scalar(), decode_segment(), decode_sgirle8(), decode_short_vertical_delta(), decode_short_vertical_delta2(), decode_sigpass(), decode_slice(), decode_speedhq_field(), decode_subband(), decode_subband_slice_buffered(), decode_subframe(), decode_unit(), decode_v4_vector(), decode_wmv9(), decode_ybr(), decode_ybr10(), decode_ybr10i(), decode_ybri(), decode_ybyr(), decode_yry10(), decode_yry10i(), decompose(), decompose2D(), decompress_i(), decompress_i3(), decompress_p(), decompress_p3(), decompress_texture_thread(), decompress_texture_thread_internal(), decorrelate(), deemphasis_c(), deflate(), deflate16(), deflicker16(), deflicker8(), deInterlaceBlendLinear(), deInterlaceFF(), deInterlaceInterpolateCubic(), deInterlaceInterpolateLinear(), deInterlaceL5(), deInterlaceMedian(), deinterleave(), denoise_depth(), denoise_spatial(), denoise_temporal(), dequant(), dequantization_float(), dequantization_int(), dequantization_int_97(), dequantize(), dequantize_slice_buffered(), dering(), diff_pixels_mvi(), diff_planes(), dilation(), dilation16(), dirac_hpel_filter(), dirac_unpack_block_motion_data(), disp_palette(), displace_packed(), displace_planar(), display_frame(), display_integral(), dist_scale(), distance(), distortion_correction_filter_slice(), divide3(), dnn_execute_layer_conv2d(), dnn_execute_layer_depth2space(), dnxhd_decode_macroblock(), dnxhd_decode_row(), dnxhd_encode_fast(), dnxhd_encode_rdo(), dnxhd_find_qscale(), dnxhd_mb_var_thread(), dnxhd_switch_matrix(), do_8tap_2d_c(), do_a_deblock_C(), do_bilin_2d_c(), do_block_ssd(), do_block_ssd16(), do_chromahold16_slice(), do_chromahold_slice(), do_chromakey16_slice(), do_chromakey_slice(), do_colorhold_slice(), do_colorkey_slice(), do_convolve(), do_despill_slice(), do_imdct(), do_lumakey_slice16(), do_lumakey_slice8(), do_scaled_8tap_c(), do_swizzle(), do_vertical_columns(), doVertDefFilter(), doVertLowPass(), downscale(), draw_axis_rgb(), draw_axis_yuv(), draw_bar_rgb(), draw_bar_yuv(), draw_carpet_slice(), draw_curves(), draw_dc(), draw_dot(), draw_frame(), draw_glyph(), draw_glyphs(), draw_gradients_slice(), draw_gradients_slice16(), draw_htext(), draw_htext16(), draw_ihtext(), draw_ihtext16(), draw_legend(), draw_line(), draw_mandelbrot(), draw_n_color(), draw_response(), draw_spatial(), draw_text(), draw_trace16(), draw_trace8(), draw_triangle_slice(), draw_vtext(), draw_vtext16(), drawline(), drawtext(), dual_inner_prod(), dump_curves(), dump_fir(), dv_calc_mb_coordinates(), dv_decode_video_segment(), dvb_encode_rle2(), dvb_encode_rle4(), dvb_encode_rle8(), dvd_encode_rle(), dwt_haar(), dwt_plane(), dx2_decode_slice_410(), dx2_decode_slice_420(), dx2_decode_slice_444(), dx2_decode_slice_5x5(), dx2_decode_slice_rgb(), dxn3dc_block(), dxt1_block_internal(), dxt2_block(), dxt3_block_internal(), dxt4_block(), dxt5_block_internal(), dxt5y_block(), dxt5ys_block(), encode_15_7_sl(), encode_block(), encode_blocks(), encode_cblk(), encode_clnpass(), encode_codebook(), encode_dvb_subtitles(), encode_frame(), encode_gbrp10(), encode_gbrp12(), encode_line(), encode_mode(), encode_plane(), encode_q_branch(), encode_q_branch2(), encode_refpass(), encode_rgb48_10bit(), encode_rgb_frame(), encode_scalar(), encode_sigpass(), encode_slice(), encode_subband(), encode_subband_c0run(), encode_tile(), enlarge_roq_mb4(), envelope_instant(), envelope_instant16(), envelope_peak(), envelope_peak16(), epic_decode_pixel_pred(), epic_decode_run_length(), epic_decode_tile(), epic_handle_edges(), epic_predict_from_NW_NE(), ereflectx(), erosion(), erosion16(), estimate_sid_gain(), eval_expr(), eval_motion_dist(), eval_poly(), evalfunc_0(), evalfunc_1(), event_loop(), export_plane(), extract_from_packed(), extract_m8(), extract_m8_i16(), factorization(), ff_apply_motion_4x4(), ff_apply_motion_8x8(), ff_apply_vector_2x2(), ff_apply_vector_4x4(), ff_avc_find_startcode_internal(), ff_avg_h264_chroma_mc2_msa(), ff_avg_h264_chroma_mc4_mmi(), ff_avg_h264_chroma_mc4_msa(), ff_avg_h264_chroma_mc8_mmi(), ff_avg_h264_chroma_mc8_msa(), ff_avg_no_rnd_vc1_chroma_mc4_mmi(), ff_avg_no_rnd_vc1_chroma_mc8_mmi(), ff_calculate_bounding_box(), ff_cbrt(), ff_clear_fixed_vector(), ff_clz_c(), ff_copy_rectangle(), ff_draw_rectangle(), ff_emulated_edge_mc(), ff_er_frame_end(), ff_eval_poly(), ff_exp10(), ff_exp10f(), ff_exp2fi(), ff_fast_powf(), ff_fill_rectangle(), ff_fix_long_mvs(), ff_fix_long_p_mvs(), ff_get_best_fcode(), ff_gmc_c(), ff_gradfun_blur_line_c(), ff_gradfun_filter_line_c(), ff_h263_decode_frame(), ff_h263_encode_motion_vector(), ff_h263_pred_acdc(), ff_h263_pred_dc(), ff_h263_round_chroma(), ff_h264_alloc_tables(), ff_h264_slice_context_init(), ff_hevc_dsp_init_neon(), ff_hevc_hls_filter(), ff_hevc_hls_mvd_coding(), ff_idet_filter_line_c(), ff_idet_filter_line_c_16bit(), ff_intra_pred_8_16x16_msa(), ff_intra_pred_8_32x32_msa(), ff_ivi_dc_col_slant(), ff_ivi_dc_haar_2d(), ff_ivi_dc_row_slant(), ff_ivi_dc_slant_2d(), ff_ivi_put_pixels_8x8(), ff_ivi_recompose53(), ff_ivi_recompose_haar(), ff_jpeg2000_set_significance(), ff_jpegls_decode_picture(), ff_libwebp_get_frame(), ff_llrint(), ff_lrint(), ff_mdct_calc_c(), ff_mdct_calcw_c(), ff_me_search_ds(), ff_me_search_epzs(), ff_me_search_esa(), ff_me_search_fss(), ff_me_search_hexbs(), ff_me_search_ntss(), ff_me_search_tdls(), ff_me_search_tss(), ff_me_search_umh(), ff_mediacodec_sw_buffer_copy_yuv420_packed_semi_planar_64x32Tile2m8ka(), ff_mjpeg_find_marker(), ff_mpeg4_encode_mb(), ff_mss12_decode_rect(), ff_mxf_decode_pixel_layout(), ff_print_debug_info2(), ff_put_h264_chroma_mc2_msa(), ff_put_h264_chroma_mc4_mmi(), ff_put_h264_chroma_mc4_msa(), ff_put_h264_chroma_mc8_mmi(), ff_put_h264_chroma_mc8_msa(), ff_put_no_rnd_vc1_chroma_mc4_mmi(), ff_put_no_rnd_vc1_chroma_mc8_mmi(), ff_put_vp8_bilinear16_h_mmi(), ff_put_vp8_bilinear16_hv_mmi(), ff_put_vp8_bilinear16_v_mmi(), ff_put_vp8_bilinear4_h_mmi(), ff_put_vp8_bilinear4_hv_mmi(), ff_put_vp8_bilinear4_v_mmi(), ff_put_vp8_bilinear8_h_mmi(), ff_put_vp8_bilinear8_hv_mmi(), ff_put_vp8_bilinear8_v_mmi(), ff_put_vp8_epel16_h4_mmi(), ff_put_vp8_epel16_h4v4_mmi(), ff_put_vp8_epel16_h4v6_mmi(), ff_put_vp8_epel16_h6_mmi(), ff_put_vp8_epel16_h6v4_mmi(), ff_put_vp8_epel16_h6v6_mmi(), ff_put_vp8_epel16_v4_mmi(), ff_put_vp8_epel16_v6_mmi(), ff_put_vp8_epel4_h4_mmi(), ff_put_vp8_epel4_h4v4_mmi(), ff_put_vp8_epel4_h4v6_mmi(), ff_put_vp8_epel4_h6_mmi(), ff_put_vp8_epel4_h6v4_mmi(), ff_put_vp8_epel4_h6v6_mmi(), ff_put_vp8_epel4_v4_mmi(), ff_put_vp8_epel4_v6_mmi(), ff_put_vp8_epel8_h4_mmi(), ff_put_vp8_epel8_h4v4_mmi(), ff_put_vp8_epel8_h4v6_mmi(), ff_put_vp8_epel8_h6_mmi(), ff_put_vp8_epel8_h6v4_mmi(), ff_put_vp8_epel8_h6v6_mmi(), ff_put_vp8_epel8_v4_mmi(), ff_put_vp8_epel8_v6_mmi(), ff_rint(), ff_rle_encode(), ff_rm_parse_packet(), ff_rm_reorder_sipr_data(), ff_rtjpeg_decode_frame_yuv420(), ff_scene_sad16_c(), ff_scene_sad_c(), ff_set_fixed_vector(), ff_snow_horizontal_compose97i(), ff_snow_inner_add_yblock(), ff_snow_pred_block(), ff_sws_alphablendaway(), ff_t_sqrt(), ff_vfscanf(), ff_vorbis_nth_root(), ff_vorbis_ready_floor1_list(), ff_vp3dsp_set_bounding_values(), ff_vp6_filter_diag4_c(), ff_vp9_fill_mv(), ffintscan(), fft_vertical(), fic_decode_slice(), fill_block(), fill_from_cache(), fill_in_tongue(), fill_loopfilter_buffers(), fill_optable(), fill_pixels(), fill_rectangle(), fill_sierpinski(), fill_tile4(), fill_tileX(), fill_yuv_image(), filter(), filter16_3x3(), filter16_5x5(), filter16_7x7(), filter16_brng(), filter16_prewitt(), filter16_roberts(), filter16_row(), filter16_sobel(), filter16_tout(), filter16_vrep(), filter181(), filter8_brng(), filter8_tout(), filter8_vrep(), filter_2_1(), filter_3x3(), filter_5x5(), filter_7x7(), filter_8tap_2d_fn(), filter_color(), filter_color2(), filter_edge(), filter_edge_16bit(), filter_edges(), filter_edges_16bit(), filter_frame(), filter_horizontally(), filter_intra(), filter_intra_16bit(), filter_line_c(), filter_line_c_16bit(), filter_mb_dir(), filter_mono(), filter_plane2d(), filter_plane3d1(), filter_plane3d2(), filter_plane_cols(), filter_plane_rows(), filter_prewitt(), filter_rgb24(), filter_rgb48(), filter_rgba(), filter_rgba64(), filter_roberts(), filter_row(), filter_slice(), filter_slice_packed(), filter_slice_planar(), filter_sobel(), filter_stereo(), filter_surround(), filter_tout_outlier(), filter_xyz(), final_block_filtering(), find_and_decode_index(), find_block_motion(), find_codec(), find_codec_by_name(), find_headers_search(), find_min_max(), find_min_max_16(), find_min_max_planar(), find_min_max_planar_16(), find_motion(), find_quant_thread(), find_slice_quant(), fir_to_phase(), fixed_borders16(), fixed_exp(), fixed_log(), fixed_sqrt(), flashsv_decode_frame(), flat(), flat16(), float_near_ulp(), float_y_to_uint_y_wrapper(), flush_encoders(), fmodl(), for(), forward_transform(), frame_analysis(), frame_block_to_cell(), frame_synthesis(), frand(), freq2bark(), freq_test(), full_search(), funny_diamond_search(), g2m_paint_cursor(), g_func(), gather_data_for_subcel(), gaussian_for(), gbr16ptopacked16(), gbr24ptopacked24(), gbr24ptopacked32(), gbraptopacked32(), gen_image(), generate_half_size_image(), generate_noise(), generate_round_keys(), generate_window_func(), get_4block_rd(), get_alpha_data(), get_amv(), get_badness(), get_block_bits(), get_block_rd(), get_block_row(), get_block_row16(), get_cbphi(), get_dc(), get_frame_mb(), get_huffman_group(), get_input(), get_intra_count(), get_len(), get_limits(), get_natural_factor(), get_opcodes(), get_output(), get_pcm(), get_pixel16_uv(), get_pixel_uv(), get_qcx(), get_qPy(), get_rac_count(), get_response(), get_rice_ook(), get_sad_ob(), get_sae(), get_sbad(), get_sbad_ob(), get_siz(), get_slice_data(), get_sub_picture(), get_tile_pos(), get_time(), get_visual_weight(), get_volume(), getfilter_float(), getimag(), getnmsedec_ref(), getnmsedec_sig(), getpix(), getpix_integrate(), getpix_integrate_internal(), getreal(), getSSD(), gif_image_write_image(), gif_parse_packet(), global_mv(), graticule16_row(), graticule_row(), gray2rgb(), green_graticule(), green_graticule16(), h261_loop_filter(), h263_v_loop_filter_c(), h264_export_enc_params(), halfpel_interpol(), hammer_to_xyz(), handle_p_frame_apng(), hard_thresholding(), hermite_interpolation(), hex_char_to_number(), hex_search(), hexfloat(), hls_coding_unit(), horiz_slice_c(), horizontal_compose53i(), horizontal_compose_daub97i(), horizontal_compose_dd137i(), horizontal_compose_dd97i(), horizontal_compose_dirac53i(), horizontal_compose_fidelityi(), horizontal_compose_haari(), horizontal_decompose53i(), hp_output(), hq_decode_mb(), hqa_decode_mb(), hqx_decode_422(), hqx_decode_422a(), hqx_decode_444(), hqx_decode_444a(), hqx_filter(), huffman_decode(), hypot(), hysteresis16(), hysteresis8(), hz_2_rad(), iblend_hline(), iblend_hline16(), idcin_decode_vlcs(), idct_mb(), idct_put(), idraw_htext(), idraw_htext16(), idraw_vtext(), idraw_vtext16(), ifft_vertical(), image_copy_16_to_8(), imagf(), import_plane(), inflate(), inflate16(), init(), init_axis_color(), init_block_mapping(), init_context_frame(), init_cqt(), init_dequant4_coeff_table(), init_dequant8_coeff_table(), init_dequant_tables(), init_filter(), init_gaussian_filter(), init_multbl2(), init_mv_table(), init_obmc_weight_row(), init_ref(), init_volume(), inter_predict(), inter_recon(), interleave_cols_to_any(), interpol(), interpolate(), interpolate_bilinear16(), interpolate_bilinear8(), INTERPOLATE_METHOD(), intra_pred(), intra_pred_down_left(), intra_pred_down_right(), intra_pred_lp(), intra_pred_lp_left(), intra_pred_lp_top(), intra_pred_plane(), intra_predict(), intra_recon(), inv_cdf(), inverse_adpcm(), inverse_prediction(), inverse_transform(), invert_graticule(), invert_graticule16(), ipol(), ipvideo_decode_block_opcode_0x2(), ipvideo_decode_block_opcode_0x3(), ipvideo_decode_block_opcode_0x4(), ipvideo_decode_block_opcode_0x5(), ipvideo_decode_block_opcode_0x6_16(), ipvideo_decode_block_opcode_0x7(), ipvideo_decode_block_opcode_0x7_16(), ipvideo_decode_block_opcode_0x8(), ipvideo_decode_block_opcode_0x8_16(), ipvideo_decode_block_opcode_0x9(), ipvideo_decode_block_opcode_0x9_16(), ipvideo_decode_block_opcode_0xA(), ipvideo_decode_block_opcode_0xA_16(), ipvideo_decode_block_opcode_0xB_16(), ipvideo_decode_block_opcode_0xC(), ipvideo_decode_block_opcode_0xC_16(), ipvideo_decode_block_opcode_0xD_16(), ipvideo_decode_block_opcode_0xE_16(), ipvideo_decode_block_opcode_0xF(), ipvideo_decode_format_06_opcodes(), ipvideo_decode_format_10_opcodes(), ipvideo_decode_format_11_opcodes(), is_image_translucent(), is_inside(), is_same1(), is_same1_16(), is_same3(), is_same3_16(), is_same4(), is_same4_16(), isansicode(), isVertMinMaxOk_C(), iterative_me(), ivi_init_tiles(), ivi_output_plane(), ivi_process_empty_tile(), izero(), jpeg2000_decode_packets_po_iteration(), jpeg2000_decode_tile(), jpg_unescape(), l2s_dia_search(), lag_calc_zero_run(), lagfun_frame16(), lagfun_frame8(), lanczos_kernel(), lerp_color(), lerp_color16(), libopenjpeg_copy_packed12(), libopenjpeg_copy_packed16(), libopenjpeg_copy_packed8(), libopenjpeg_copy_to_packed16(), libopenjpeg_copy_to_packed8(), libopenjpeg_copy_unpacked16(), libopenjpeg_copy_unpacked8(), libopenjpeg_copyto16(), libopenjpeg_copyto8(), libx265_encode_set_roi(), limiter16(), limiter8(), lininterp(), ljpeg_decode_yuv_scan(), ljpeg_encode_bgr(), ljpeg_encode_yuv_mb(), load_palette(), lowpass(), lowpass16(), LR128(), lrint(), lrintf(), lrintf_mips(), ls_decode_line(), ls_encode_line(), lum(), luma_abs_diff(), lumsum(), m101_decode_frame(), MAC64(), magy_decode_slice(), magy_decode_slice10(), main(), make_lpf(), make_point(), map(), maskedmax16(), maskedmax8(), maskedmerge16(), maskedmerge8(), maskedmin16(), maskedmin8(), match_colors(), mc_block(), mc_chroma_scaled(), mc_chroma_unscaled(), mc_luma_scaled(), mc_luma_unscaled(), mc_row(), mc_subpel(), median_frames16(), median_frames8(), midequalizer16(), midequalizer8(), mirror_borders16(), mirror_borders8(), mix_frames(), mjpeg_decode_scan(), MLS64(), mm_decode_inter(), mm_decode_intra(), modplug_read_packet(), motion_compensation(), mp_decode_line(), mp_get_yuv_from_rgb(), mp_read_changes_map(), mp_set_rgb_from_yuv(), mpeg4_decode_sprite_trajectory(), mss2_decode_frame(), mss3_decode_frame(), mss4_decode_frame(), mulinv(), multiply3x3_c(), mv_mp_mode_mx(), mv_mp_mode_mx_lt(), mv_test(), mxf_compute_essence_containers(), mxf_compute_ptses_fake_index(), mxf_essence_container_end(), mxg_find_startmarker(), nearest_sample_index(), nlmeans_slice(), noise(), nsse16_c(), nsse8_c(), op(), open_filter_param(), optimize_colors(), output_plane(), output_single_frame(), overlay_opencl_blend(), p8idct(), packed16togbra16(), packedtogbr24p(), parse_channel_name(), parse_cinespace(), parse_points(), parse_psfile(), parse_transform_color_indexing(), passed(), pcx_decode_frame(), pick_color16(), pick_color8(), pick_palette_entry(), pick_pixel1(), pick_pixel1_16(), pick_pixel3(), pick_pixel3_16(), pick_pixel4(), pick_pixel4_16(), picmemset(), picmemset_8bpp(), pitch_downsample(), pix_norm1_c(), pixel2float48(), pixel_belongs_to_box(), pixel_diff(), pixscope_filter_frame(), planar2x_c(), planar8ToP01xleWrapper(), planarToP01xWrapper(), plot_freq(), plot_spectrum_column(), png_get_interlaced_row(), png_put_interlaced_row(), pointer_at(), pop(), postProcess(), postprocess_current_frame(), pow_m1_4(), pp_postprocess(), pre_calculate_col(), pred_angular(), pred_block_dc(), pred_block_mode(), pred_dc(), pred_mv(), pred_planar(), pred_sbsplit(), predict_slice(), predict_slice_buffered(), predictor_calc_error(), predictor_init_state(), prelut_interp_1d_linear(), premultiply16(), premultiply16offset(), premultiply16yuv(), premultiply8(), premultiply8offset(), premultiply8yuv(), pRNG(), process(), process_16(), process_bayer(), process_c(), process_cqt(), process_line0(), process_planar(), process_planar_16(), process_slice_uyvy422(), process_slice_yuv420p(), process_slice_yuv422p(), process_slice_yuv444p(), propagate_block_data(), prores_fdct(), pseudocolor_filter(), pseudocolor_filter_10(), pseudocolor_filter_10d(), pseudocolor_filter_11(), pseudocolor_filter_11d(), pseudocolor_filter_16(), pseudocolor_filter_16_10(), pseudocolor_filter_16_10d(), pseudocolor_filter_16_11(), pseudocolor_filter_16_11d(), push(), put_blocks(), put_cursor(), put_dc(), put_hevc_epel_bi_h(), put_hevc_epel_bi_hv(), put_hevc_epel_bi_v(), put_hevc_epel_bi_w_h(), put_hevc_epel_bi_w_hv(), put_hevc_epel_bi_w_v(), put_hevc_epel_h(), put_hevc_epel_hv(), put_hevc_epel_uni_h(), put_hevc_epel_uni_hv(), put_hevc_epel_uni_v(), put_hevc_epel_uni_w_h(), put_hevc_epel_uni_w_hv(), put_hevc_epel_uni_w_v(), put_hevc_epel_v(), put_hevc_pel_bi_pixels(), put_hevc_pel_bi_w_pixels(), put_hevc_pel_pixels(), put_hevc_pel_uni_w_pixels(), put_hevc_qpel_bi_h(), put_hevc_qpel_bi_hv(), put_hevc_qpel_bi_v(), put_hevc_qpel_bi_w_h(), put_hevc_qpel_bi_w_hv(), put_hevc_qpel_bi_w_v(), put_hevc_qpel_h(), put_hevc_qpel_hv(), put_hevc_qpel_uni_h(), put_hevc_qpel_uni_hv(), put_hevc_qpel_uni_v(), put_hevc_qpel_uni_w_h(), put_hevc_qpel_uni_w_hv(), put_hevc_qpel_uni_w_v(), put_hevc_qpel_v(), put_no_rnd_vc1_chroma_mc4_c(), put_no_rnd_vc1_chroma_mc8_c(), put_obmc(), put_pcm(), put_pixel(), put_signed_rect_clamped_8bit_c(), qcom_tile_pos(), qdmc_decode_init(), qexpneg(), qian_thresholding(), qtrle_decode_1bpp(), qtrle_decode_2n4bpp(), quant_band_template(), quantize(), r_func(), ratecontrol_1pass(), raw_decode(), raw_encode(), rd_frame(), read16_fft_bin(), read8_fft_bin(), read_fft_data(), read_mv_component(), read_table(), read_uncompressed_sgi(), read_vitc_line(), realf(), reconstruct_and_encode_image(), refill2(), refine_colors(), reflectx(), remove_doubling(), render_charset(), render_default_font(), render_freetype(), render_line(), render_line_unrolled(), render_point(), render_slice(), request_frame(), resample_cubic(), resample_linear(), restore_tqb_pixels(), restore_tree(), reverse_dc_prediction(), rgb15to16(), rgb15to16_c(), rgb16to15(), rgb16to15_c(), rgb24_to_yuv420p(), rgb24tobgr24(), rgb24tobgr24_c(), rgb2yuv(), rgb2yuv_fsb(), rgb48Toxyz12(), rgb_from_cqt(), rgb_to_xy(), rgtc2_block_internal(), rgtc_block_internal(), rice_decompress(), ring1_test(), ring2_test(), rint(), rle_uncompress(), rnnoise_channel(), roqvideo_decode_frame(), round(), roundf(), run_postproc(), sab_diamond_search(), safe_log(), sao_band_filter(), sao_edge_filter(), sao_edge_restore_0(), sao_edge_restore_1(), sao_filter_CTB(), sbc_analyze_1b_8s_simd_even(), sbc_analyze_1b_8s_simd_odd(), sbc_analyze_4b_4s_simd(), sbc_analyze_4b_8s_simd(), sbc_analyze_audio(), sbc_calc_scalefactors(), sbc_calc_scalefactors_j(), sbc_enc_process_input_4s(), sbc_enc_process_input_8s(), sbr_autocorrelate_c(), sbr_hf_gen(), sbr_neg_odd_64_c(), sbr_qmf_analysis(), sbr_sum_square_c(), scalbnl(), scaled_filter_8tap_fn(), scaledown(), scaleup(), scaleup_rev(), scanexp(), search(), search_boundary(), seqvideo_decode(), set_blocks(), set_frame(), set_frame_data(), set_pixel1(), set_pixel1_16(), set_pixel3(), set_pixel3_16(), set_pixel4(), set_pixel4_16(), set_roi_map(), set_src_position(), setup_3x3(), setup_5x5(), setup_7x7(), setup_column(), setup_pps(), setup_row(), sgi_rle_encode(), sigmoid_approx(), silk_decode_frame(), silk_is_lpc_stable(), silk_lsf2lpc(), skip_check(), slice_geq_filter(), small_diamond_search(), smear_borders16(), smoothstep(), soft_thresholding(), softfloat_mul(), spatial_compensation_0(), spatial_compensation_1(), spatial_compensation_10(), spatial_compensation_11(), spatial_compensation_2(), spatial_compensation_3(), spatial_compensation_4(), spatial_compensation_5(), spatial_compensation_6(), spatial_compensation_7(), spatial_compensation_8(), spatial_compensation_9(), spatial_compose53i_dy_buffered(), square(), square_quadratic(), square_sum(), sse(), ssim_4x4x2_core(), ssim_4x4xn_16bit(), ssim_4x4xn_8bit(), ssim_plane(), stereo_position(), stereo_transform(), stereographic_to_xyz(), store_slice16_c(), store_slice2_c(), store_slice_c(), sub2video_copy_rect(), sub_left_prediction(), subband_coeffs(), subimage_alpha_with_fill(), subimage_with_fill(), subimage_with_fill_template(), subsampling_bounds(), sunrast_decode_frame(), sunrast_image_write_image(), super2xsai(), svq1_decode_block_intra(), svq1_decode_block_non_intra(), svq1_decode_delta_block(), svq1_decode_frame(), svq1_decode_motion_vector(), svq1_encode_plane(), svq1_motion_inter_4v_block(), svq1_motion_inter_block(), svq1_skip_block(), svq3_decode_init(), svq3_mc_dir(), svq3_mc_dir_part(), sws_printVec2(), sws_scale(), synth_window(), tansig_approx(), targa_decode_rle(), tdsc_decode_jpeg_tile(), tdsc_decode_tiles(), tdsc_paint_cursor(), tempNoiseReducer(), temporal_luma_motion_vector(), test_autocorrelate(), test_motion(), test_neg_odd_64(), test_sum_square(), tex2D(), tgq_decode_frame(), tgv_decode_inter(), threshold16(), threshold8(), tile_codeblocks(), tile_do_block(), tmv_decode_frame(), to_meta_with_crop(), tonemap(), tonemap_slice(), transform_rdpcm(), transformed_point(), transpose_block_16_c(), transpose_block_24_c(), transpose_block_32_c(), transpose_block_48_c(), transpose_block_64_c(), transpose_block_8_c(), truemotion2rt_decode_frame(), trunc(), truncf(), try_push_frame(), try_push_frames(), tspyramid_to_xyz(), uint_y_to_float_y_wrapper(), ulti_convert_yuv(), ulti_decode_frame(), ulti_grad(), ulti_pattern(), umh_search(), unpack_coeffs(), unpremultiply16(), unpremultiply16offset(), unpremultiply16yuv(), unpremultiply8(), unpremultiply8offset(), unpremultiply8yuv(), unsharp_opencl_make_filter_params(), unsharp_slice(), update_context(), update_histogram_diff(), update_histogram_frame(), update_rice(), update_sono_rgb(), update_sono_yuv(), upmix_1_0(), upmix_2_1(), upmix_3_0(), upmix_3_1(), upmix_3_1_surround(), upmix_4_0(), upmix_4_1(), upmix_5_0_back(), upmix_5_1_back(), upmix_5_1_back_2_1(), upmix_5_1_back_surround(), upmix_6_0(), upmix_6_1(), upmix_7_0(), upmix_7_1(), upmix_stereo(), v_block_filter(), var_diamond_search(), var_size_bmc(), var_size_bme(), vb_decode_framedata(), vblur(), vc1_pack_bitplanes(), vc2_subband_dwt_53(), vc2_subband_dwt_97(), vcr1_decode_frame(), vectorscope16(), vectorscope8(), vertX1Filter(), very_broken_op(), vibrance_slice16(), vibrance_slice8(), video_audio_display(), decklink_input_callback::VideoInputFrameArrived(), vp56_mc(), vp6_block_variance(), vp6_filter_hv4(), vp8_lossy_decode_alpha(), vqa_decode_chunk(), vu9_to_vu12(), vu9_to_vu12_c(), weight_averages(), weight_U(), weight_V(), weight_Y(), which_edge(), WORD_VEC(), write_palette(), write_text(), X264_frame(), x8_loop_filter(), xan_wc3_copy_pixel_run(), xan_wc3_decode_frame(), xan_wc3_output_pixel_run(), xbr_filter(), xcbgrab_reposition(), xcorr_kernel(), xcorrelate(), xcorrelate_fast(), xcorrelate_slow(), xpm_decode_close(), xpm_decode_frame(), xvid_encode_close(), xvid_encode_frame(), xvid_encode_init(), xvid_ff_2pass_create(), xyz12Torgb48(), xyz_to_hammer(), xyz_to_pannini(), xyz_to_stereographic(), xyz_to_tetrahedron(), yao_subblock(), yop_decode_frame(), yuv2planeX_8_16(), yuv2planeX_u(), yuv2rgb(), yuv2yuv(), yuv_from_cqt(), yvu9_to_yuy2(), yvu9_to_yuy2_c(), zero12v_decode_frame(), zmbv_decode_xor_16(), zmbv_decode_xor_32(), zmbv_decode_xor_8(), and zmbv_me().

◆ rw

FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug rw

◆ r

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite***************************************** If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug o r

Definition at line 150 of file fate.txt.

◆ w

FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug o o w

Definition at line 150 of file fate.txt.

Referenced by __align__(), aac_encode_frame(), acalc_magnitudes(), add_bytes(), add_bytes_c(), add_bytes_l2_c(), add_entry1(), add_hfyu_left_pred_bgr32_c(), add_hfyu_median_pred_int16_c(), add_int16_c(), add_lag_median_prediction(), add_left_pred_c(), add_left_pred_int16_c(), add_median_pred_c(), add_median_prediction(), add_waves(), add_yblock(), adjust_frame_information(), all_black(), all_same(), all_white(), alloc_buffers(), alloc_frame(), alloc_frame_empty(), alloc_sequence_buffers(), analyze_plane(), apply_delogo(), apply_intensity_stereo(), apply_luma_lut(), apply_luma_lut10(), apply_lut(), apply_lut10(), apply_mid_side_stereo(), apply_palette(), apply_tns(), apply_window_int16_c(), av_bmg_get(), av_expr_parse(), av_image_alloc(), av_image_check_sar(), av_image_check_size(), av_image_check_size2(), av_image_fill_black(), av_opt_is_set_to_default(), av_opt_set_image_size(), av_read_image_line(), av_read_image_line2(), av_vdpau_get_surface_parameters(), av_write_image_line(), av_write_image_line2(), avg_c(), avg_h264_qpel8_v_lowpass_mmi(), avg_h264_qpel8or16_hv2_lowpass_mmi(), avoid_clipping(), avpriv_dnxhd_get_hr_frame_size(), avpriv_mirror(), blend_line(), blend_line16(), blend_line_hv(), blend_line_hv16(), blend_pixel(), blend_pixel16(), blur(), blur_image(), blur_pixel(), bswap_buf(), build_filter(), calc_channel_magnitudes(), calc_persp_luts(), calc_thr_3gpp(), calculate_sums(), cas_slice16(), cas_slice8(), cbs_av1_read_ns(), cbs_av1_write_ns(), cdg_copy_rect_buf(), cdg_fill_rect_preset(), cdg_fill_wrapper(), cdxl_decode_frame(), celt_postfilter_apply_transition(), channel_weighting(), check_add_bytes(), check_add_gradient_pred(), check_add_int16(), check_add_left_pred(), check_add_left_pred_16(), check_add_median_pred(), check_eq(), check_header(), check_hflip(), check_idct_dc4(), check_intra_mode(), check_multiply3x3(), check_rgb2yuv(), check_threshold(), check_yuv2rgb(), check_yuv2yuv(), checkasm_check_nlmeans(), checkasm_check_vf_gblur(), choose_rct_params(), clip_interval(), clv_decode_init(), codebook_trellis_rate(), color_correlation(), color_correlation_gbrp(), color_decorrelation(), color_decorrelation_gbrp(), color_mix(), compose(), compose2D(), compose2D2(), compute_dar(), compute_default_clut(), compute_histogram16(), compute_histogram8(), compute_metric(), compute_safe_ssd_integral_image_c(), compute_ssd_integral_image(), compute_unsafe_ssd_integral_image(), config_input(), config_input_main(), config_output(), config_props(), constrain_rgb(), convert(), convert_mask_to_strength_mask(), convolution_x(), convolve_avg_horiz_mmi(), convolve_avg_mmi(), convolve_avg_vert_mmi(), convolve_horiz_mmi(), convolve_vert_mmi(), copy_avg_fn(), copy_c(), copy_cell(), copy_CTB_to_hv(), copy_picture_field(), copy_region_enc(), copy_rev(), correlate(), correlate_slice_buffered(), cover_rect(), create_clusters(), create_frame(), cudascale_config_props(), d3d11va_transfer_data(), dc_test(), dct_quantize_refine(), deband_16_c(), deband_16_coupling_c(), deband_8_c(), deband_8_coupling_c(), decode_555(), decode_block(), decode_blocks(), decode_byte_vertical_delta(), decode_delta_d(), decode_delta_e(), decode_delta_j(), decode_delta_l(), decode_dlta(), decode_dvd_subtitles(), decode_entropy_coded_image(), decode_ext_header(), decode_fint(), decode_frame(), decode_frame_header(), decode_hextile(), decode_hybrid(), decode_init(), decode_inter_plane(), decode_line(), decode_long_vertical_delta(), decode_long_vertical_delta2(), decode_mous(), decode_move(), decode_mvc2(), decode_plane(), decode_q_branch(), decode_rgb_frame(), decode_rle(), decode_sequence_header_adv(), decode_short_horizontal_delta(), decode_short_vertical_delta(), decode_short_vertical_delta2(), decode_slice(), decode_subband_slice_buffered(), decode_tns(), decode_wmv9(), decompose(), decompose2D(), decompose2D2(), decorrelate(), deflicker16(), deflicker8(), deinterleaveBytes_c(), denoise_depth(), denoise_spatial(), denoise_temporal(), dequantization_float(), dequantization_int(), dequantization_int_97(), dequantize(), dequantize_slice_buffered(), diff_bytes(), diff_bytes_c(), diff_int16_c(), diff_planes(), displace_packed(), displace_planar(), display_integral(), dng_decode_jpeg(), dnn_execute_layer_pad(), dnxhd_probe(), do_8tap_2d_c(), do_bilin_2d_c(), do_convolve(), do_lumakey_slice16(), do_lumakey_slice8(), do_scaled_8tap_c(), doTest(), double_threshold(), dpx_probe(), draw_arrow(), draw_axis_rgb(), draw_axis_yuv(), draw_background(), draw_bar_rgb(), draw_bar_yuv(), draw_curves(), draw_dc(), draw_edges_8_c(), draw_legend(), draw_line(), draw_response(), draw_spatial(), dup_wchar_to_utf8(), dvb_encode_rle2(), dvb_encode_rle4(), dvb_encode_rle8(), dvd_encode_rle(), dvdsub_parse_extradata(), dwt_decode53(), dwt_decode97_float(), dwt_decode97_int(), dwt_encode53(), dwt_encode97_float(), dwt_encode97_int(), dxa_probe(), dxa_read_header(), dxtory_decode_v1_410(), dxtory_decode_v1_420(), dxtory_decode_v1_444(), encode_band_info(), encode_block(), encode_blocks(), encode_dvb_subtitles(), encode_ext_header(), encode_flush(), encode_frame(), encode_line(), encode_ms_info(), encode_plane(), encode_q_branch(), encode_q_branch2(), encode_rgb_frame(), encode_scale_factors(), encode_spectral_coeffs(), encode_subband_c0run(), encode_thread(), encode_window_bands_info(), ereflectx(), extend_edges(), extract_line(), ff_aac_adjust_common_pred(), ff_aac_apply_tns(), ff_aac_encode_tns_info(), ff_aac_is_encoding_err(), ff_aac_search_for_is(), ff_aac_search_for_ltp(), ff_aac_search_for_tns(), ff_add_png_paeth_prediction(), ff_attributes_dump(), ff_big_add(), ff_big_div(), ff_big_mul(), ff_blend_rectangle(), ff_boxblur_eval_filter_params(), ff_calculate_bounding_box(), ff_copy_rectangle(), ff_copy_rectangle2(), ff_default_get_video_buffer(), ff_draw_rectangle(), ff_emulated_edge_mc(), ff_fill_line_with_color(), ff_fill_rectangle(), ff_get_video_buffer(), ff_h263_decode_frame(), ff_idet_filter_line_c(), ff_idet_filter_line_c_16bit(), ff_init_nextband_map(), ff_intrax8_common_end(), ff_intrax8_common_init(), ff_intrax8_decode_picture(), ff_jpeg2000_tag_tree_init(), ff_jpegls_decode_picture(), ff_libwebp_get_frame(), ff_load_image(), ff_mjpeg_decode_frame(), ff_mpadsp_apply_window(), ff_mspel_motion(), ff_null_get_video_buffer(), ff_pnm_decode_header(), ff_pns_bits(), ff_printGUID(), ff_rle_encode(), ff_rm_parse_packet(), ff_rtjpeg_decode_frame_yuv420(), ff_rtp_send_jpeg(), ff_scale_adjust_dimensions(), ff_simple_idct_axp(), ff_snow_alloc_blocks(), ff_snow_common_init_after_header(), ff_snow_pred_block(), ff_spdif_bswap_buf16(), ff_sws_alphablendaway(), ff_vc1_decode_entry_point(), ff_vc1_decode_sequence_header(), ff_vmafmotion_init(), ff_vp9_decode_block(), ff_wmv2_add_mb(), ff_wmv2_common_init(), ff_wmv2_decode_mb(), ff_wmv2_decode_picture_header(), ff_wmv2_decode_secondary_picture_header(), ff_wmv2_encode_mb(), ff_wmv2_encode_picture_header(), ffmal_copy_frame(), ffprobe_show_library_versions(), ffprobe_show_pixel_formats(), ffprobe_show_program_version(), fileTest(), fill_buf(), fill_in_tongue(), fill_loopfilter_buffers(), fill_pixels(), fill_rectangle(), fill_slice_long(), filter(), filter16_brng(), filter16_tout(), filter16_vrep(), filter8_brng(), filter8_tout(), filter8_vrep(), filter_8tap_2d_fn(), filter_channel(), filter_edges(), filter_edges_16bit(), filter_frame(), filter_frame16(), filter_frame8(), filter_line_c(), filter_line_c_16bit(), filter_mbedge(), filter_slice(), find_smallest_bounding_rectangle(), find_tongue(), finish_file(), flush(), for(), fov_from_dfov(), fraps2_decode_plane(), free_adaptation_sets(), g2m_paint_cursor(), gaussian_blur(), gen_image(), get_4block_rd(), get_alpha_data(), get_block_bits(), get_block_rd(), get_dc(), get_input(), get_intra_count(), get_output(), get_response(), get_slice_data(), get_video_buffer(), get_x(), getpix(), getpix_integrate(), getpix_integrate_internal(), getSSD(), gif_copy_img_rect(), gif_crop_translucent(), gif_fill_rect(), guess_dc(), h_block_filter(), halfpel_interpol(), hammer_to_xyz(), hblur(), hflip_b24_c(), hflip_b48_c(), hflip_byte_c(), hflip_dword_c(), hflip_qword_c(), hflip_short_c(), horizontal_compose_daub97i(), horizontal_compose_dd137i(), horizontal_compose_dd97i(), horizontal_compose_dirac53i(), horizontal_compose_fidelityi(), horizontal_compose_haar0i(), horizontal_compose_haar1i(), horizontal_compose_haari(), hpel_motion_lowres(), hqa_decode_slice(), hqx_filter(), hwmap_get_buffer(), hysteresis16(), hysteresis8(), idcin_probe(), image_copy_16_to_8(), image_sad(), implicit_weight_table(), ingenient_read_packet(), init(), init_cqt(), init_decoder(), init_imdct_window(), init_noise(), init_pattern_from_file(), init_pattern_from_string(), init_planes(), interleave(), interleaveBytes(), interleaveBytes_c(), irdft_horizontal16(), irdft_horizontal8(), iterative_me(), ivi_output_plane(), jpeg_create_header(), kmvc_decode_inter_8x8(), kmvc_decode_intra_8x8(), left_prediction(), lift(), liftS(), limiter16(), limiter8(), load_input_picture(), load_mask(), lpc_apply_welch_window_c(), ls_decode_line(), ls_encode_line(), lut_packed_16bits(), lut_packed_8bits(), lut_planar_16bits(), lut_planar_8bits(), magicyuv_median_pred16(), main(), mark_pns(), mask_edges(), maskedclamp_slice(), maskedmax16(), maskedmax8(), maskedmerge16(), maskedmerge8(), maskedmin16(), maskedmin8(), maskedminmax_slice(), mc_chroma_scaled(), mc_chroma_unscaled(), mc_luma_scaled(), mc_luma_unscaled(), monochrome_color_location(), mp_decode_line(), mp_read_changes_map(), mpeg4_decode_dpcm_macroblock(), mpeg4_decode_sprite_trajectory(), mpeg_decode_sequence_display_extension(), mpv_reconstruct_mb_internal(), mss2_blit_wmv9_c(), mss2_blit_wmv9_masked_c(), mss2_blit_wmv9_template(), mss2_decode_frame(), mss2_gray_fill_masked_c(), multiply3x3_c(), nlmeans_opencl_filter_frame(), nlmeans_plane(), noise(), non_maximum_suppression(), nppscale_config_props(), on2avc_apply_ms(), on2avc_decode_band_scales(), on2avc_read_channel_data(), on2avc_read_ms_info(), output_single_frame(), pack_yuv(), paint_raw(), paint_rect(), pam_encode_frame(), parse_adaptation_sets(), parse_mb_skip(), parse_presentation_segment(), passed(), pcx_decode_frame(), pgmyuv_save(), pick_palette_entry(), pix_norm1(), pix_sum(), pixlet_decode_frame(), pixscope_filter_frame(), plot_freq(), plot_gamuts(), plot_white_point(), png_filter_row(), pop_greys(), postprocess_chroma(), postprocess_luma(), predict_slice(), predict_slice_buffered(), premultiply16(), premultiply16offset(), premultiply16yuv(), premultiply8(), premultiply8offset(), premultiply8yuv(), print_pkt_side_data(), print_results(), probe(), process_c(), process_command(), process_frame(), process_frame_obj(), psy_3gpp_analyze_channel(), ptx_decode_frame(), push(), push_greys(), push_single_pic(), put_cursor(), put_h264_qpel8_v_lowpass_mmi(), put_h264_qpel8or16_hv1_lowpass_mmi(), put_h264_qpel8or16_hv2_lowpass_mmi(), put_ics_info(), qcom_tile_pos(), qsvscale_config_props(), quantize(), quantize_band_cost_cached(), ratecontrol_1pass(), rdft_horizontal16(), rdft_horizontal8(), read_interval_packets(), read_packets(), read_shape_from_file(), realloc_texture(), reflectx(), request_frame(), resample_cubic(), resample_linear(), rescale(), rgb2yuv(), rgb2yuv_fsb(), rle_uncompress(), roi_scale_cblk(), rv30_parse_slice_header(), rv40_parse_picture_size(), rv40_parse_slice_header(), sao_filter_CTB(), scaled_filter_8tap_fn(), scaledown(), scaleup(), scaleup_rev(), scroll_slice(), search_for_ms(), search_for_pns(), search_for_quantizers_anmr(), search_for_quantizers_fast(), search_for_quantizers_twoloop(), selfTest(), set_blocks(), set_dimensions(), set_frame(), set_special_band_scalefactors(), set_sps(), setctx_2d(), setup_3x3(), setup_5x5(), setup_7x7(), setup_row(), sgi_rle_encode(), show_chapters(), show_error(), show_format(), show_frame(), show_log(), show_packet(), show_program(), show_programs(), show_stream(), show_streams(), show_subtitle(), show_tags(), shrink22(), shrink44(), shrink88(), silk_decode_frame(), snow_horizontal_compose_lift_lead_out(), snow_horizontal_compose_liftS_lead_out(), sobel(), sse(), sse_mb(), sub2video_copy_rect(), sub2video_prepare(), sub_hfyu_median_pred_int16_c(), sub_left_prediction(), sub_left_prediction_bgr32(), sub_left_prediction_rgb24(), sub_median_pred_c(), sub_median_prediction(), sub_png_paeth_prediction(), subsampling_bounds(), sunrast_decode_frame(), svq3_decode_init(), tag_tree_size(), tag_tree_zero(), targa_decode_rle(), targa_encode_normal(), targa_encode_rle(), tdsc_decode_jpeg_tile(), tdsc_decode_tiles(), tdsc_paint_cursor(), tdsc_parse_tdsf(), threshold16(), threshold8(), threshold_slice(), tm2_decode_blocks(), tongue_outline(), tqi_decode_frame(), transfer_image_buf(), transpose_block_16_c(), transpose_block_24_c(), transpose_block_32_c(), transpose_block_48_c(), transpose_block_64_c(), transpose_block_8_c(), try_8x8basis_c(), txd_decode_frame(), unpack_coeffs(), unpack_yuv(), unpremultiply16(), unpremultiply16offset(), unpremultiply16yuv(), unpremultiply8(), unpremultiply8offset(), unpremultiply8yuv(), update_canvas_size(), update_frame_pool(), update_size(), update_sono_rgb(), update_sono_yuv(), upsample_plane_c(), v210_decode_slice(), v210_enc(), v_block_filter(), vblur(), vc2_encode_init(), vectorscope16(), vectorscope8(), verify_md5(), vfw_read_header(), video_audio_display(), video_open(), vmd_probe(), vp8_lossless_decode_frame(), vp9_handle_packet(), vu9_to_vu12(), vu9_to_vu12_c(), w_c(), wavpack_encode_sample(), webm_dash_manifest_write_header(), webp_write_packet(), webp_write_trailer(), weight_averages(), weighted_avg_elliott_mul5_m16(), WINDOW_FUNC(), wma_lsp_to_curve(), wmv2_add_block(), wmv2_decode_end(), wmv2_decode_init(), wmv2_decode_inter_block(), wmv2_decode_motion(), wmv2_encode_init(), wmv2_mspel8_v_lowpass(), wmv2_pred_motion(), wnv1_get_code(), write_adaptation_set(), write_header(), write_representation(), write_root_table(), x8_ac_compensation(), x8_decode_intra_mb(), x8_get_ac_rlf(), x8_get_dc_rlf(), x8_get_orient_vlc(), x8_get_prediction(), x8_get_prediction_chroma(), x8_init_block_index(), x8_reset_vlc_tables(), x8_select_ac_table(), x8_setup_spatial_predictor(), x8_update_predictions(), xcbgrab_reposition(), xsub_encode_rle(), yuv2rgb(), yuv2yuv(), yvu9_to_yuy2(), and yvu9_to_yuy2_c().

◆ org

FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg org

Definition at line 153 of file fate.txt.

◆ to

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite***************************************** If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg can be set to

◆ 

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite***************************************** If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg can be set or •

Definition at line 184 of file fate.txt.

◆ tests

FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg can be set or it has a meaning only while running the regression tests ‘THREADS’ Specify how many threads to use while running regression it is quite useful to detect thread related regressions ‘THREAD_TYPE’ Specify which threading strategy either ‘slice’ or by default ‘slice frame’ ‘CPUFLAGS’ Specify CPU flags ‘TARGET_EXEC’ Specify or override the wrapper used to run the tests The ‘TARGET_EXEC’ option provides a way to run FATE wrapped in ‘qemu user’ or ‘wine’ or on remote targets through ‘ssh’ ‘GEN’ Set to ‘1’ to generate the missing or mismatched references ‘HWACCEL’ Specify which hardware acceleration to use while running regression tests

Definition at line 188 of file fate.txt.

Referenced by checkasm_check_h264pred(), and main().

◆ ‘frame’

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite***************************************** If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg can be set or it has a meaning only while running the regression tests ‘THREADS’ Specify how many threads to use while running regression it is quite useful to detect thread related regressions ‘THREAD_TYPE’ Specify which threading strategy either ‘slice’ or ‘frame’

Definition at line 192 of file fate.txt.

◆ ‘valgrind’

FFmpeg Automated Testing Environment************************************ Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction************** FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory********************************************** If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable 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 to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ 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 Uploading new samples to the fate suite***************************************** If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg can be set or it has a meaning only while running the regression tests ‘THREADS’ Specify how many threads to use while running regression it is quite useful to detect thread related regressions ‘THREAD_TYPE’ Specify which threading strategy either ‘slice’ or by default ‘slice frame’ ‘CPUFLAGS’ Specify CPU flags ‘TARGET_EXEC’ Specify or override the wrapper used to run the tests The ‘TARGET_EXEC’ option provides a way to run FATE wrapped in ‘valgrind’

Definition at line 201 of file fate.txt.