diff options
author | V3n3RiX <venerix@redcorelinux.org> | 2019-01-22 10:09:44 +0000 |
---|---|---|
committer | V3n3RiX <venerix@redcorelinux.org> | 2019-01-22 10:09:44 +0000 |
commit | 09351e78166b5e864197c4456ebae3f89dd0bed9 (patch) | |
tree | 41a96399f56ed3aa399006871bfce4430db84aa2 /media-libs/gstreamer/files | |
parent | c8a77dfe4d3d307c1d5dd2650b7297447d8b609d (diff) |
gentoo resync : 22.01.2019
Diffstat (limited to 'media-libs/gstreamer/files')
-rw-r--r-- | media-libs/gstreamer/files/1.14.3-fix-gstsegment-test.patch | 46 |
1 files changed, 0 insertions, 46 deletions
diff --git a/media-libs/gstreamer/files/1.14.3-fix-gstsegment-test.patch b/media-libs/gstreamer/files/1.14.3-fix-gstsegment-test.patch deleted file mode 100644 index 9b2fb2402e1b..000000000000 --- a/media-libs/gstreamer/files/1.14.3-fix-gstsegment-test.patch +++ /dev/null @@ -1,46 +0,0 @@ -From 0a479c3cdc5d5745b6cc5084d5faf3b0ab8e604a Mon Sep 17 00:00:00 2001 -From: Jan Schmidt <jan@centricular.com> -Date: Mon, 17 Sep 2018 22:13:22 +1000 -Subject: [PATCH] tests: Use a different rate in a segment test. - -Using a rate of 1.1 in the test is causing the test to -fail on 32-bit because ceil(1.1 * 10) can round to 12. - -Instead use a rate 2.0 that can be expressed as floating -point number and doesn't trigger the problem. - -https://bugzilla.gnome.org/show_bug.cgi?id=797154 ---- - tests/check/gst/gstsegment.c | 6 +++--- - 1 file changed, 3 insertions(+), 3 deletions(-) - -diff --git a/tests/check/gst/gstsegment.c b/tests/check/gst/gstsegment.c -index 17ad18c2f..751469d76 100644 ---- a/tests/check/gst/gstsegment.c -+++ b/tests/check/gst/gstsegment.c -@@ -888,7 +888,7 @@ GST_START_TEST (segment_full) - fail_unless_equals_int (pos, 190); - - /* Test a non-1.0 rate that lands right before the segment, but still +ve */ -- segment.rate = 1.1; -+ segment.rate = 2.0; - segment.start = 100; - segment.offset = 0; - segment.stop = 500; -@@ -897,11 +897,11 @@ GST_START_TEST (segment_full) - segment.time = 10000; - fail_unless (gst_segment_position_from_running_time_full (&segment, - GST_FORMAT_TIME, 140, &pos) == 1); -- fail_unless (pos == 89); -+ fail_unless (pos == 80); - /* And now one that should give a position < 0 */ - fail_unless (gst_segment_position_from_running_time_full (&segment, - GST_FORMAT_TIME, 0, &pos) == -1); -- fail_unless (pos == 65); -+ fail_unless (pos == 200); - - /* Test a non-1.0 negative rate that lands right after the (reversed) segment, but still +ve position */ - segment.rate = -2.0; --- -2.17.0 - |