[Bug 797291] New: tests: pipeline processing deadline unit test fails in valgrind

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=797291

            Bug ID: 797291
           Summary: tests: pipeline processing deadline unit test fails in
                    valgrind
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: Linux
            Status: NEW
          Severity: blocker
          Priority: Normal
         Component: gstreamer (core)
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: t.i.m at zen.co.uk
        QA Contact: gstreamer-bugs at lists.freedesktop.org
                CC: nicolas at ndufresne.ca, olivier.crete at ocrete.ca,
                    thaytan at noraisin.net
     GNOME version: ---

For me the new test_pipeline_processing_deadline unit test reliably fails in
valgrind, e.g.:

$ GST_CHECKS=test_pipeline_processing_deadline make gst/gstpipeline.valgrind
Running suite(s): GstPipeline
0%: Checks: 1, Failures: 1, Errors: 0
gst/gstpipeline.c:721:F:pipeline tests:test_pipeline_processing_deadline:0:
Pipeline position is not at least 50millisecond (reported 149976914
nanoseconds)

$ GST_CHECKS=test_pipeline_processing_deadline make gst/gstpipeline.valgrind
Running suite(s): GstPipeline
gst/gstpipeline.c:721:F:pipeline tests:test_pipeline_processing_deadline:0:
Pipeline position is not at least 50millisecond (reported 90000000 nanoseconds)

Wonder if this is expected e.g. due to tight timing and scheduling shenanigans,
or something that needs fixing or if the test should be skipped if we're
running in valgrind?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.