[Bug 735665] New: gst-validate should concatenate its issue reporting in some cases.

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=735665
  GStreamer | gst-devtools | git

           Summary: gst-validate should concatenate its issue reporting in
                    some cases.
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: Normal
         Component: gst-devtools
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: mathieu.duponchelle at epitech.eu
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Output from gst-validate can very easily reach hundreds of issues reported in
some cases.

An example of a case where the same issue is reported for successive elements
is:

gst-validate-1.0 gnlurisource
uri=file:///home/meh/gst-validate/gst-qa-assets/medias/mp4/mp3_h264.0.mp4
inpoint=0 duration=1000000000 ! fakesink

Here, we can see that the "buffer was received after EOS" issue is reported for
the h264 parser, the capsfilter and the h264 decoder.

My proposal here is to make it so the issue gets reported for the whole
subchain, in that format:

issue: buffer was received after EOS
    First detected on : <h264parse0:sink> at 0:00:00.023533513
    Same issue was detected on:
        <capsfilter0:sink> at 0:00:00.023541286
        <avdec_h264-0:sink> at 0:00:00.023543930
    Details : Received buffer 0x7ff9080b6610A after EOS
    Description : a pad shouldn't receive any more buffers after it gets EOS

I'm not sure about the "Same issue was detected" format, it could also be "Last
issue was detected on".

We could add a --verbose switch to gst-validate to still obtain the previous
behaviour.

I don't know yet how that should be implemented, let's discuss that here :)

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.