tools:validate: Concider seek in PAUSED position being not exact as WARNING

In some corner cases in GNL it is totally correct that a position in a
seek in paused is not perfectly exact
This commit is contained in:
Thibault Saunier 2014-07-24 19:03:50 +02:00
parent ae60e09a1f
commit 9a07ce7681

View file

@ -447,6 +447,7 @@ gboolean
ges_validate_activate (GstPipeline * pipeline, const gchar * scenario,
gboolean * needs_setting_state)
{
GstValidateOverride *o;
GstValidateRunner *runner = NULL;
GstValidateMonitor *monitor = NULL;
@ -523,6 +524,12 @@ ges_validate_activate (GstPipeline * pipeline, const gchar * scenario,
set_child_property_mandatory_fields,
"Allows to change child property of an object", FALSE);
o = gst_validate_override_new ();
gst_validate_override_change_severity (o,
GST_VALIDATE_ISSUE_ID_EVENT_SEEK_RESULT_POSITION_WRONG,
GST_VALIDATE_REPORT_LEVEL_WARNING);
gst_validate_override_register_by_name ("scenarios", o);
runner = gst_validate_runner_new ();
g_signal_connect (runner, "report-added",
G_CALLBACK (_validate_report_added_cb), pipeline);