Updated the documentation to explain that when the maximum threads is > 1

* glib/gthreadpool.c: Updated the documentation to explain that
when the maximum threads is > 1 the sort functionality is not 100%
accurate due to the ramdom nature of the scheduler choosing which
threads to execute. Fixes bug #334943.

* tests/threadpool-test.c: Disabled the debugging by default and
fixed the sort test to set the maximum threads to 1 to guarantee
the thread entry function is called in order.
This commit is contained in:
Martyn James Russell
2006-03-24 15:21:28 +00:00
parent 9e98598d04
commit f0ee594a80
4 changed files with 63 additions and 10 deletions

View File

@@ -1,3 +1,14 @@
2006-03-24 Martyn Russell <martyn@imendio.com>
* glib/gthreadpool.c: Updated the documentation to explain that
when the maximum threads is > 1 the sort functionality is not 100%
accurate due to the ramdom nature of the scheduler choosing which
threads to execute. Fixes bug #334943.
* tests/threadpool-test.c: Disabled the debugging by default and
fixed the sort test to set the maximum threads to 1 to guarantee
the thread entry function is called in order.
2006-03-23 Matthias Clasen <mclasen@redhat.com>
=== Branch for 2.10 ===