gstreamer/tests/old/testsuite/threads/Makefile.am

include ../Rules

tests_pass = thread1 thread2 thread3 thread4 threadf
tests_fail = thread5 threadd queue

tests_ignore = threade threadb threadc

queue_SOURCES = queue.c
queue_CFLAGS = $(AM_CFLAGS)

thread1_SOURCES = thread.c
thread1_CFLAGS = -DTESTNUM=1 $(AM_CFLAGS)
thread2_SOURCES = thread.c
thread2_CFLAGS = -DTESTNUM=2 $(AM_CFLAGS)
thread3_SOURCES = thread.c
thread3_CFLAGS = -DTESTNUM=3 $(AM_CFLAGS)
thread4_SOURCES = thread.c
thread4_CFLAGS = -DTESTNUM=4 $(AM_CFLAGS)
thread5_SOURCES = thread.c
thread5_CFLAGS = -DTESTNUM=5 $(AM_CFLAGS)
Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tes... Original commit message from CVS: Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tests pass, some fail; the expected sucess/failure is coded in the Makefile.am's. gst-register is properly run for both 'make check' and 'make distcheck'. Much of the common infrastructure is coded in testsuite/Rules. 2003-10-15 01:25:41 +00:00			`include ../Rules`
applying http://bugzilla.gnome.org/show_bug.cgi?id=110707 patch, should fix testsuite issues Original commit message from CVS: applying http://bugzilla.gnome.org/show_bug.cgi?id=110707 patch, should fix testsuite issues 2003-05-18 22:59:51 +00:00
Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tes... Original commit message from CVS: Massive patch to make 'make check' work properly. Many compilation fixes -- everything should compile now. Some tests pass, some fail; the expected sucess/failure is coded in the Makefile.am's. gst-register is properly run for both 'make check' and 'make distcheck'. Much of the common infrastructure is coded in testsuite/Rules. 2003-10-15 01:25:41 +00:00			`tests_pass = thread1 thread2 thread3 thread4 threadf`
gst/gstclock.: deprecate old interface and disable functions that aren't in use anymore. Original commit message from CVS: 2004-01-13 Benjamin Otte <in7y118@public.uni-hamburg.de> gst/gstclock.c: (gst_clock_class_init), (gst_clock_init), (gst_clock_set_speed), (gst_clock_set_active), (gst_clock_is_active), (gst_clock_reset), (gst_clock_handle_discont): * gst/gstclock.h: deprecate old interface and disable functions that aren't in use anymore. * gst/gstelement.h: * gst/gstelement.c: (gst_element_get_time), (gst_element_wait), (gst_element_set_time), (gst_element_adjust_time): add concept of "element time" and functions to get/set this time. * gst/gstelement.c: (gst_element_change_state): update element time correctly. * gst/gstelement.c: (gst_element_get_compatible_pad_filtered): This is a debug message, not a g_critical. * gst/gstpad.c: (gst_pad_event_default): handle discontinuous events right with element time. * gst/gstscheduler.c: (gst_scheduler_state_transition): update to clocking fixes. set clocks on elements in READY=>PAUSED. The old behaviour caused a wrong element time on the first element that started playing. * gst/schedulers/gstbasicscheduler.c: (gst_basic_scheduler_class_init): * gst/schedulers/gstoptimalscheduler.c: (gst_opt_scheduler_class_init): remove code that just implements the default behaviour. * gst/elements/gstfakesink.c: (gst_fakesink_chain): update to use new clocking functions * testsuite/clock/clock1.c: (gst_clock_debug), (main): * testsuite/clock/clock2.c: (gst_clock_debug), (main): update to test new element time. * gst/autoplug/gstspideridentity.c: (gst_spider_identity_getcaps): use _get_allowed_caps instead of _get_caps. This catches filtered caps correctly. * testsuite/debug/commandline.c: update for new GST_DEBUG syntax. * testsuite/threads/Makefile.am: disable a test that only works sometimes. 2004-01-14 00:46:48 +00:00			`tests_fail = thread5 threadd queue`
testsuite/Makefile.am: define tests_ignore Original commit message from CVS: * testsuite/Makefile.am: define tests_ignore * testsuite/Rules: Added new tests_ignore, which get compiled, but not run (generally because they're inconsistent or have heisenbugs). Now we can ensure all the .c files compile in testsuite/. * testsuite/bins/Makefile.am: define tests_ignore * testsuite/bytestream/Makefile.am: * testsuite/caps/Makefile.am: * testsuite/clock/Makefile.am: * testsuite/debug/Makefile.am: * testsuite/debug/global.c: (gst_debug_log_one), (gst_debug_log_two): Fix compilation problem. * testsuite/dynparams/Makefile.am: * testsuite/elements/Makefile.am: * testsuite/ghostpads/Makefile.am: * testsuite/indexers/Makefile.am: * testsuite/parse/Makefile.am: * testsuite/plugin/Makefile.am: * testsuite/refcounting/Makefile.am: * testsuite/refcounting/element_pad.c: (main): Don't return leak results, because it's not calculated correctly. * testsuite/refcounting/pad.c: (main): same * testsuite/states/Makefile.am: * testsuite/tags/Makefile.am: * testsuite/threads/Makefile.am: 2004-04-15 04:54:53 +00:00
			`tests_ignore = threade threadb threadc`
converting this to separate binaries so they can be run as a testsuite Original commit message from CVS: converting this to separate binaries so they can be run as a testsuite 2002-09-12 11:56:08 +00:00
adding simple queue test Original commit message from CVS: adding simple queue test 2003-10-03 15:21:49 +00:00			`queue_SOURCES = queue.c`
			`queue_CFLAGS = $(AM_CFLAGS)`

converting this to separate binaries so they can be run as a testsuite Original commit message from CVS: converting this to separate binaries so they can be run as a testsuite 2002-09-12 11:56:08 +00:00			`thread1_SOURCES = thread.c`
use AM_CFLAGS dummy NULL init for vars to deal with warnings Original commit message from CVS: use AM_CFLAGS dummy NULL init for vars to deal with warnings 2002-12-03 21:55:39 +00:00			`thread1_CFLAGS = -DTESTNUM=1 $(AM_CFLAGS)`
converting this to separate binaries so they can be run as a testsuite Original commit message from CVS: converting this to separate binaries so they can be run as a testsuite 2002-09-12 11:56:08 +00:00			`thread2_SOURCES = thread.c`
use AM_CFLAGS dummy NULL init for vars to deal with warnings Original commit message from CVS: use AM_CFLAGS dummy NULL init for vars to deal with warnings 2002-12-03 21:55:39 +00:00			`thread2_CFLAGS = -DTESTNUM=2 $(AM_CFLAGS)`
converting this to separate binaries so they can be run as a testsuite Original commit message from CVS: converting this to separate binaries so they can be run as a testsuite 2002-09-12 11:56:08 +00:00			`thread3_SOURCES = thread.c`
use AM_CFLAGS dummy NULL init for vars to deal with warnings Original commit message from CVS: use AM_CFLAGS dummy NULL init for vars to deal with warnings 2002-12-03 21:55:39 +00:00			`thread3_CFLAGS = -DTESTNUM=3 $(AM_CFLAGS)`
converting this to separate binaries so they can be run as a testsuite Original commit message from CVS: converting this to separate binaries so they can be run as a testsuite 2002-09-12 11:56:08 +00:00			`thread4_SOURCES = thread.c`
use AM_CFLAGS dummy NULL init for vars to deal with warnings Original commit message from CVS: use AM_CFLAGS dummy NULL init for vars to deal with warnings 2002-12-03 21:55:39 +00:00			`thread4_CFLAGS = -DTESTNUM=4 $(AM_CFLAGS)`
converting this to separate binaries so they can be run as a testsuite Original commit message from CVS: converting this to separate binaries so they can be run as a testsuite 2002-09-12 11:56:08 +00:00			`thread5_SOURCES = thread.c`
use AM_CFLAGS dummy NULL init for vars to deal with warnings Original commit message from CVS: use AM_CFLAGS dummy NULL init for vars to deal with warnings 2002-12-03 21:55:39 +00:00			`thread5_CFLAGS = -DTESTNUM=5 $(AM_CFLAGS)`