mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2025-06-06 07:28:53 +00:00
Code Issues 1 Projects Releases Wiki Activity

validate: fix some recurring typos

Browse source
This commit is contained in:
Reynaldo H. Verdejo Pinochet 2016-06-09 14:30:53 -07:00
parent 73ac07d6e3
commit 07fa1b3ca5
3 changed files with 9 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
validate/gst/validate/gst-validate-scenario.c
View file

@ -96,7 +96,7 @@ static GstValidateActionType *_find_action_type (const gchar * type_name);
/* GstValidateScenario is not really thread safe and /* GstValidateScenario is not really thread safe and
* everything should be done from the thread GstValidate * everything should be done from the thread GstValidate
* was inited from, unless stated otherwize. * was inited from, unless stated otherwise.
*/ */
struct _GstValidateScenarioPrivate struct _GstValidateScenarioPrivate
{ {
@ -449,7 +449,7 @@ _check_scenario_is_done (GstValidateScenario * scenario)
* the 'position' and 'duration' variables. And it will always convert that * the 'position' and 'duration' variables. And it will always convert that
* value to a GstClockTime. * value to a GstClockTime.
* *
* Returns: %TRUE if the time value could be retrieved/computed or %FALSE otherwize * Returns: %TRUE if the time value could be retrieved/computed or %FALSE otherwise
*/ */
gboolean gboolean
gst_validate_action_get_clocktime (GstValidateScenario * scenario, gst_validate_action_get_clocktime (GstValidateScenario * scenario,
@ -504,7 +504,7 @@ gst_validate_action_get_clocktime (GstValidateScenario * scenario,
* *
* For more information you should have a look at #gst_event_new_seek * For more information you should have a look at #gst_event_new_seek
* *
* Returns: %TRUE if the seek could be executed, %FALSE otherwize * Returns: %TRUE if the seek could be executed, %FALSE otherwise
*/ */
gboolean gboolean
gst_validate_scenario_execute_seek (GstValidateScenario * scenario, gst_validate_scenario_execute_seek (GstValidateScenario * scenario,
@ -2937,7 +2937,7 @@ gst_validate_list_scenarios (gchar ** scenarios, gint num_scenarios,
done: done:
result = g_key_file_to_data (kf, &datalength, &err); result = g_key_file_to_data (kf, &datalength, &err);
g_print ("All scenarios avalaible:\n%s", result); g_print ("All scenarios available:\n%s", result);
if (output_file && !err) if (output_file && !err)
g_file_set_contents (output_file, result, datalength, &err); g_file_set_contents (output_file, result, datalength, &err);

2
validate/gst/validate/gst-validate-utils.c
View file

@ -699,7 +699,7 @@ done:
* for the value, if it is a double, it considers the value to be in second * for the value, if it is a double, it considers the value to be in second
* it can be a gint, gint64 a guint, a gint64. * it can be a gint, gint64 a guint, a gint64.
* *
* Return: %TRUE in case of success, %FALSE otherwize. * Return: %TRUE in case of success, %FALSE otherwise.
*/ */
gboolean gboolean
gst_validate_utils_get_clocktime (GstStructure * structure, const gchar * name, gst_validate_utils_get_clocktime (GstStructure * structure, const gchar * name,

8
validate/launcher/main.py
View file

@ -74,7 +74,7 @@ you will need that tool to get started.
--------------------------- ---------------------------
To implement new tests, you will just need to set the media path using the To implement new tests, you will just need to set the media path using the
--medias-paths argument. If you want to run all avalaible scenarios on all the --medias-paths argument. If you want to run all available scenarios on all the
file present in that folder, you should run the first time: file present in that folder, you should run the first time:
. $gst-validate-launcher --medias-paths /path/to/media/files --generate-media-info . $gst-validate-launcher --medias-paths /path/to/media/files --generate-media-info
@ -240,7 +240,7 @@ class LauncherConfig(Loggable):
try: try:
subprocess.check_output("gdb --help", shell=True) subprocess.check_output("gdb --help", shell=True)
except subprocess.CalledProcessError: except subprocess.CalledProcessError:
printc("Want to use gdb, but not avalaible on the system", printc("Want to use gdb, but not available on the system",
Colors.FAIL) Colors.FAIL)
return False return False
@ -303,7 +303,7 @@ class LauncherConfig(Loggable):
try: try:
subprocess.check_output("valgrind --help", shell=True) subprocess.check_output("valgrind --help", shell=True)
except subprocess.CalledProcessError: except subprocess.CalledProcessError:
printc("Want to use valgrind, but not avalaible on the system", printc("Want to use valgrind, but not available on the system",
Colors.FAIL) Colors.FAIL)
return False return False
@ -355,7 +355,7 @@ if it succeeded loading the tests, False otherwise.
You will be able to configure the TestManager with its various methods. This You will be able to configure the TestManager with its various methods. This
function will be called with each TestManager usable, for example you will be function will be called with each TestManager usable, for example you will be
passed the 'validate' TestManager in case the GstValidateManager launcher is passed the 'validate' TestManager in case the GstValidateManager launcher is
avalaible. You should configure it using: available. You should configure it using:
* test_manager.add_scenarios: which allows you to register a list of scenario names to be run * test_manager.add_scenarios: which allows you to register a list of scenario names to be run
* test_manager.set_default_blacklist: Lets you set a list of tuple of the form: * test_manager.set_default_blacklist: Lets you set a list of tuple of the form: