On Thu, 28 Mar 2013, Anton Khirnov  wrote:

Module: libav
Branch: master
Commit: 33942b7bdedaf0c7017f84245f4928860319a584

Author:    Anton Khirnov <[email protected]>
Committer: Anton Khirnov <[email protected]>
Date:      Wed Mar 13 11:03:08 2013 +0100

FATE: add a test for the channelmap filter

---

tests/fate/filter.mak         |    7 +++++++
tests/filtergraphs/channelmap |    1 +
2 files changed, 8 insertions(+), 0 deletions(-)

diff --git a/tests/fate/filter.mak b/tests/fate/filter.mak
index 120dc61..89a1140 100644
--- a/tests/fate/filter.mak
+++ b/tests/fate/filter.mak
@@ -33,6 +33,13 @@ fate-filter-asyncts: REF = 
$(SAMPLES)/nellymoser/nellymoser-discont.pcm
FATE_FILTER_VSYNTH-$(CONFIG_BOXBLUR_FILTER) += fate-filter-boxblur
fate-filter-boxblur: CMD = framecrc -c:v pgmyuv -i $(SRC) -vf boxblur=2:1

+FATE_FILTER-$(call FILTERDEMDECENCMUX, CHANNELMAP, WAV, PCM_S16LE, PCM_S16LE, 
WAV) += fate-filter-channelmap
+fate-filter-channelmap: SRC = $(TARGET_PATH)/tests/data/asynth-44100-6.wav
+fate-filter-channelmap: tests/data/asynth-44100-6.wav
+fate-filter-channelmap: CMD = md5 -i $(SRC) -filter_complex_script 
$(SRC_PATH)/tests/filtergraphs/channelmap -f wav -flags +bitexact
+fate-filter-channelmap: CMP = oneline
+fate-filter-channelmap: REF = 21f1977c4f9705e2057083f84764e685
+
fate-filter-delogo: CMD = framecrc -i $(SAMPLES)/real/rv30.rm -vf 
delogo=show=0:x=290:y=25:w=26:h=16 -an

This fails in some of my remote testing setups.

Previously, one was expected to have the fate samples available at the same path on both host and remote (since the remote obviously reads samples from there and decodes them, but the host needs them for comparing decoding output for the fuzzy tests), and the build dir could be mapped via --target-path. But this now also requires $(SRC_DIR) to exist at the same path on the target.

Not sure if this is an issue worth fixing, or if I just should suck it up and make sure the src dir is mapped (and on the same path) on the target as well.

// Martin
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to