El 6 d’abril de 2012 1:00, Steven Chamberlain ha escrit:
> Hi,
>
> Just made an observation to be wary of: connection-test doesn't always
> fail. It actually seems to be about 50-50 for me, on kfreebsd-i386
> 8.3~svn230343-1 with 4-way SMP.
That's to be expected. The test is passing a CLOCK_MO
Hi,
Just made an observation to be wary of: connection-test doesn't always
fail. It actually seems to be about 50-50 for me, on kfreebsd-i386
8.3~svn230343-1 with 4-way SMP.
Example of success:
> steven@kfreebsd-i386:~/libsoup2.4-2.38.0$ tests/connection-test -d
>
> Invalid Content-Length fra
El 20 de març de 2012 21:38, Steven Chamberlain ha escrit:
> I've narrowed down the context-test failures to g_cond_wait_until [1]
> returning false without actually waiting until the requested time.
This suggests pthread_cond_timedwait buggyness. I'll investigate this.
> Under gdb we hit a fam
El 22 de març de 2012 19:58, Robert Millan ha escrit:
> This smells like #662018.
>
> I'll see if I can spend some time on it (this weekend if noone beats me to
> it).
Please could someone test this? It's not correct, but it should do the trick.
--
Robert Millan
Index: eglibc-2.13/linuxthread
Hi again,
I've narrowed down the context-test failures to g_cond_wait_until [1]
returning false without actually waiting until the requested time.
Test case with extra debug info:
> time = g_get_monotonic_time () + 5 * G_TIME_SPAN_SECOND;
> debug_printf (1, " g_cond_wait_until %lu\n", t
Hi,
I've run the failing tests with -d option on kfreebsd-i386 to try to get
some more detail:
> $ ./context-test -d
>
> Test 1: blocking the main thread does not block other thread
> (Using SOUP_SESSION_ASYNC_CONTEXT)
> timeout!
>
> Test 2: blocking the main thread does not block other threa
6 matches
Mail list logo
