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

include ../Rules

tests_pass = thread1 thread2 thread3 thread4 thread5 threadb threadd threade threadf threadg
tests_fail = 
# threadh

tests_ignore = queue threadc
# staticrec

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
Reworked the GstThread implementation, make more operations threadsafe and more reliable. Original commit message from CVS: * gst/gstthread.c: (gst_thread_dispose), (gst_thread_sync), (gst_thread_change_state), (gst_thread_child_state_change), (gst_thread_main_loop): * gst/gstthread.h: * testsuite/threads/Makefile.am: * testsuite/threads/queue.c: * testsuite/threads/thread.c: (construct_pipeline), (change_state), (main): * testsuite/threads/threadc.c: (construct_pipeline): * testsuite/threads/threadd.c: (main): * testsuite/threads/threade.c: (main): * testsuite/threads/threadf.c: Reworked the GstThread implementation, make more operations threadsafe and more reliable. Moved testcases from the failing to the working list. 2004-09-06 15:57:11 +00:00			`tests_pass = thread1 thread2 thread3 thread4 thread5 threadb threadd threade threadf threadg`
unbreak testsuite Original commit message from CVS: unbreak testsuite 2004-09-08 23:37:07 +00:00			`tests_fail =`
			`# threadh`
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
unbreak testsuite Original commit message from CVS: unbreak testsuite 2004-09-08 23:37:07 +00:00			`tests_ignore = queue threadc`
			`# staticrec`
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)`