validate: don't override max-latency if config contains multiple structs
authorGuillaume Desmottes <guillaume.desmottes@collabora.com>
Thu, 7 Feb 2019 16:34:56 +0000 (17:34 +0100)
committerThibault Saunier <tsaunier@gnome.org>
Tue, 12 Feb 2019 02:21:14 +0000 (02:21 +0000)
gst_validate_utils_get_clocktime() is resetting the value if it's not
present in the struct so we were overriding it on the next iterations.

validate/gst/validate/gst-validate-scenario.c

index fa7be9d..dc224fb 100644 (file)
@@ -3306,8 +3306,12 @@ _load_scenario_file (GstValidateScenario * scenario,
   /* max-latency and max-dropped can be overriden using config */
   for (config = gst_validate_plugin_get_config (NULL); config;
       config = g_list_next (config)) {
+    GstClockTime max_latency;
+
     gst_validate_utils_get_clocktime (config->data, "max-latency",
-        &priv->max_latency);
+        &max_latency);
+    if (GST_CLOCK_TIME_IS_VALID (max_latency))
+      priv->max_latency = max_latency;
 
     gst_structure_get_int (config->data, "max-dropped", &priv->max_dropped);
   }