luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-11-10 03:16:17 +01:00
Code Issues Packages Projects Releases Wiki Activity

tests: Fix closure-refcount to preserve old semantics

Browse Source 
The threads used to iterate at least 10000 times before setting the
"seen thread" flag to true. After porting they inadvertently did that
in the first iteration.
This commit is contained in:
Krzesimir Nowak 2019-02-28 07:05:27 +01:00
parent 70cfc9d24c
commit d687a45704
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gobject/tests/closure-refcount.c
View File

@ -183,7 +183,7 @@ thread1_main (gpointer user_data)
TestClosureRefcountData *data = user_data;
guint i = 0;
for (i = 0; !g_atomic_int_get (&data->stopping); i++)
for (i = 1; !g_atomic_int_get (&data->stopping); i++)
{
test_closure (data->closure);
if (i % 10000 == 0)
@ -202,7 +202,7 @@ thread2_main (gpointer user_data)
TestClosureRefcountData *data = user_data;
guint i = 0;
for (i = 0; !g_atomic_int_get (&data->stopping); i++)
for (i = 1; !g_atomic_int_get (&data->stopping); i++)
{
test_closure (data->closure);
if (i % 10000 == 0)
@ -291,7 +291,7 @@ test_closure_refcount (void)
* thread1 and thread2. Even though @n_iterations is high, we can’t guarantee
* that the scheduler allocates time fairly (or at all!) to thread1 or
* thread2. */
for (i = 0;
for (i = 1;
i < n_iterations ||
!g_atomic_int_get (&test_data.seen_thread1) ||
!g_atomic_int_get (&test_data.seen_thread2);