Tim Janik 10a3867a6e test high contention on closure reference counts to trigger and catch
Mon Aug  1 23:33:47 2005  Tim Janik  <timj@imendio.com>

        * tests/refcount/closures.c: test high contention on closure
        reference counts to trigger and catch non-atomic updates.

        * tests/refcount/objects.c:
        * tests/refcount/objects2.c:
        * tests/refcount/properties.c:
        * tests/refcount/properties2.c:
        * tests/refcount/signals.c:
        fixed up test and threading fundamentals. variables accessed from all
        threads need to be volatile. context switches are enforced by using
        g_thread_yield(), not g_usleep(1) which may result in busy waits on
        some platforms. for testcode, always consider all warnings and
        critical messages fatal. issue the currently running program on
        stdout. improved progress indicators.

        * tests/refcount/properties.c:
        * tests/refcount/objects.c:
        don't overdo the number of testing threads to keep the testing machine
        usable, 2 threads can produce as much contention as 20 if executing the
        same code.

        * tests/refcount/signals.c: only start 1 thread per object. GObject
        doesn't provide mutually exclusive object access, but only mutually
        exclusive reference count modification.

        * tests/Makefile.am: added closures test.
2005-08-01 21:47:15 +00:00
..
2005-05-09 18:21:02 +00:00
2005-06-27 21:18:38 +00:00
2005-03-14 06:01:51 +00:00
2005-07-14 05:20:14 +00:00
2005-03-10 17:12:35 +00:00
2005-07-14 05:20:14 +00:00
2001-11-26 19:08:46 +00:00
2004-04-15 13:58:29 +00:00
2005-07-14 05:20:14 +00:00
2005-01-24 17:35:44 +00:00
2005-07-14 05:20:14 +00:00
2002-10-15 22:16:57 +00:00