El 6 d’abril de 2012 1:00, Steven Chamberlain ste...@pyro.eu.org 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
El 20 de març de 2012 21:38, Steven Chamberlain ste...@pyro.eu.org 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
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
El 23 de març de 2012 2:24, Steven Chamberlain ste...@pyro.eu.org ha escrit:
I don't /think/ it worked.
I didn't have enough disk space to rebuild eglibc entirely. I built
only libc0.1-i686, with your patch, and replaced only the libpthread
library on my system and re-tested. The same
El 20 de març de 2012 21:38, Steven Chamberlain ste...@pyro.eu.org ha escrit:
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, time);
if (g_cond_wait_until (test1_cond, test1_mutex, time))
El 22 de març de 2012 19:58, Robert Millan r...@debian.org 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:
On 22/03/12 20:23, Robert Millan wrote:
Please could someone test this? It's not correct, but it should do the trick.
Hi,
I don't /think/ it worked.
I didn't have enough disk space to rebuild eglibc entirely. I built
only libc0.1-i686, with your patch, and replaced only the libpthread
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 thread
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,
9 matches
Mail list logo
