Part-of: <!256>

Thibault Saunier authored Sep 10, 2021 and GStreamer Marge Bot committed Sep 10, 2021

gst_validate_get_config is transfer-container only

Part-of: <!255>

Edward Hervey authored Aug 20, 2021 and Edward Hervey committed Aug 20, 2021

This avoids memory corruption in users of that structure which
were (rightfullly) assuming static fields (such as name) wouldn't
change. Without this, they would be using strings which will have been freed in
the meantime.

Part-of: <!252>

Edward Hervey authored Jul 15, 2021 and Edward Hervey committed Jul 15, 2021

The position field of GstSegment is meant for private usage within
elements. Don't compare the values of it when doing media-check.

Part-of: <!251>

And add the tracer to the plugins list so it can be used in our
uninstalled environment.

Part-of: <!250>

Part-of: <!248>

Part-of: <!248>

Making its usage more friendly

Part-of: <!248>

We used to only support ranges, but we want to allow iterating over
values in an array too.

Part-of: <!248>

Part-of: <!248>

No reason not to use directy the GstCaps serialization function here
This commits avoids needing regenerated all expectations to remove
the `;` which is not generated anymore as it is simple and makes
merging simpler.

Part-of: <!248>

Philippe Normand authored May 20, 2021 and GStreamer Marge Bot committed May 25, 2021

Now the function returns either a fakeaudiosink or a fakevideosink, depending on
the media type.

Part-of: <!246>

Otherwise change in element implementations could lead to meaningless
breakages

Part-of: <!235>

Part-of: <!235>

Thibault Saunier authored Jan 12, 2021 and GStreamer Marge Bot committed May 14, 2021

GObject don't have such method!

Part-of: <!235>

Each test can now use a config file for
the given media file used to test.

Part-of: <!243>

Instead of the deprecated gst_element_get_request_pad.

Part-of: <!241>

Edward Hervey authored Apr 19, 2021 and Edward Hervey committed Apr 19, 2021

This was always meant to be `on-message=eos` (like in fast_forward.scenario)

Fixes #58

Part-of: <!240>

volatile is not sufficient to provide atomic guarantees and real atomics
should be used instead.  GCC 11 has started warning about using volatile
with atomic operations.

https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1719

Discovered in gst-plugins-good#868

Part-of: <!238>

Part-of: <!237>

The default number of jobs to use is half of the available cores
rounded down, but in situations where only one core is available (such
as under some VMs), this means that `gst-validate-launcher` defaults
to using zero jobs, a case that the test-running code is not prepared
to handle.

This change makes the code match the documentation for the `--jobs` option,
guards against negative values both in the default setting and in argument
parsing, and introduces some defensive programming to prevent other situations
where the code might try to use zero jobs.

Part-of: <!154>

This is not legal

Part-of: <!234>

And port the deeply nested tests we have

Part-of: <!233>

And port the deeply nested tests we have

Part-of: <!233>

Part-of: <!233>

Allowing more precise filtering of the message we are waiting for.

Part-of: <!233>

Allowing application to know when a specific action is done.

Part-of: <!233>

Part-of: <!233>

This is useful for applications that use Validate directly.

Part-of: <!233>

Part-of: <!233>

Philippe Normand authored Nov 29, 2020 and GStreamer Marge Bot committed Dec 09, 2020

Part-of: <!229>

Thibault Saunier authored Dec 08, 2020 and GStreamer Marge Bot committed Dec 08, 2020

Handling the refcounting the same whether the action is blocking or not
as we were leaking a ref for non-blocking waits.

Part-of: <!231>

Thibault Saunier authored Dec 08, 2020 and GStreamer Marge Bot committed Dec 08, 2020

Part-of: <!231>

Thibault Saunier authored Dec 08, 2020 and GStreamer Marge Bot committed Dec 08, 2020

Part-of: <!231>

Thibault Saunier authored Nov 30, 2020 and GStreamer Marge Bot committed Dec 08, 2020

And recursively

Part-of: <!231>