GNOME Bugzilla – Bug 763665
validate: Checking segment.time after a seek broke the GES testsuite
Last modified: 2016-04-29 12:56:56 UTC
Running: gst-validate-launcher ges will raise many error like: Critical error After an accurate seek, got: 0:00:00.000000000 Expected: 0:00:01.500000004 since: commit ef4635fe519cd2e9460a4ee8a34cc4fff9309741 Author: Edward Hervey <edward@centricular.com> Date: Tue Mar 8 10:49:43 2016 +0100 monitor: Add critical issue for checking accurate seek results If an accurate seek is accepted, the resulting segment.time should be exactly the requested seek start value.. https://bugzilla.gnome.org/show_bug.cgi?id=763299
Guess on IRC yesterday was that seeks are happening "too fast", so that we compare a newer seek with a segment that was caused by a previous seek.
commit 5598d3d5dd4bf7b359f925ea0c3cc98ae9acd56d Author: Thibault Saunier <thibault.saunier@collabora.com> Date: Tue Mar 22 12:07:08 2016 +0100 validate: pad-monitor: Check right segment after seek After a seek we need to wait for the right segment (meaning the segment with seqnum == last seek/flush stop seqnum) to check whether the segment.time has been properly set.