From aa4fe27657462742943dfbd185a18c223ae4dca3 Mon Sep 17 00:00:00 2001 From: James Almer Date: Mon, 2 Oct 2017 21:40:59 -0300 Subject: fate: disable fate-svq3-2 The first frame changes depending on --enable-memory-poisoning being used to configure ffmpeg or not, even if requesting bitexact decoding. Disable the test until this is fixed. Signed-off-by: James Almer --- tests/fate/qt.mak | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'tests/fate/qt.mak') diff --git a/tests/fate/qt.mak b/tests/fate/qt.mak index 2a7fc2e..c054129 100644 --- a/tests/fate/qt.mak +++ b/tests/fate/qt.mak @@ -52,7 +52,8 @@ fate-svq1-headerswap: CMD = framecrc -i $(TARGET_SAMPLES)/svq1/ct_ending_cut.mov FATE_SVQ3 += fate-svq3-1 fate-svq3-1: CMD = framecrc -i $(TARGET_SAMPLES)/svq3/Vertical400kbit.sorenson3.mov -t 6 -an -FATE_SVQ3 += fate-svq3-2 +#FATE_SVQ3 += fate-svq3-2 +#FIXME: first frame changes depending on --enable-memory-poisoning being used to configure or not fate-svq3-2: CMD = framecrc -flags +bitexact -ignore_editlist 1 -i $(TARGET_SAMPLES)/svq3/svq3_decoding_regression.mov -an FATE_SVQ3 += fate-svq3-watermark -- cgit v1.1