Source-Version: 2.46.0-2
connection-test now succeeds for me on kfreebsd-amd64, as well as
context-test (which was failing intermittently before).
This may be related to the following bits mentioned in the NEWS file:
> Changes in libsoup from 2.44.0 to 2.44.1:
> * Fixed a sporadic failu
found 663056 libsoup2.4/2.38.0
blocks 663056 by 667687
thanks
Hi,
I can confirm the eglibc patch in http://bugs.debian.org/663056#77 fixes
test/context-test for me on kfreebsd-i386.
But there is still an issue with libsoup2.4's tests/connection-test
failing 25% of the time on my system, with:
>
El 6 d’abril de 2012 3:53, Steven Chamberlain ha escrit:
> On 05/04/12 22:11, Robert Millan wrote:
>> forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=673607
>
> glib2.0 2.32.0-3 with the patch you posted there has fixed libsoup2.4's
> context-test for me. Is that what you expected?
Yep.
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
On 05/04/12 22:11, Robert Millan wrote:
> forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=673607
glib2.0 2.32.0-3 with the patch you posted there has fixed libsoup2.4's
context-test for me. Is that what you expected?
That just leaves the intermittent failures of connection-test.
Regards
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
clone 663056 -1 -2
retitle -1 confusing g_cond_wait_until() API (and docs) invites to
unintentional abuse
severity -1 normal
reassign -1 libglib2.0-dev
forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=673607
retitle -2 optional pthread_condattr_setclock() facility is not implemented
severity
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 24 de març de 2012 1:46, Steven Chamberlain ha escrit:
> On 23/03/12 22:13, Robert Millan wrote:
>> Actually it's in librt.
>
> Swapping that library with a patched version didn't change anything
> either. I'll try over the weekend to find space to do a full rebuild +
> normal dpkg install of
On 23/03/12 22:13, Robert Millan wrote:
> Actually it's in librt.
Swapping that library with a patched version didn't change anything
either. I'll try over the weekend to find space to do a full rebuild +
normal dpkg install of eglibc though.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
El 23 de març de 2012 2:24, Steven Chamberlain 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 problem as before.
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
librar
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'm trying it now, but I didn't realise eglibc would take more than 2
hours to build... or so much disk space.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To
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
El 20 de març de 2012 21:38, Steven Chamberlain 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))
>>
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
Hi porters,
since I haven't received a reply so for since my last request for help,
I'll try again.
libsoup2.4 in experimental currently ftbfs on kfreebsd-* due to errors
in the test suite. libsoup is an important package in the GNOME stack
(e.g. webkit depends on it), so the current build failur
Source: libsoup2.4
Version: 2.37.90-1
Severity: serious
User: debian-bsd@lists.debian.org
Usertags: kfreebsd
The libsoup test-suite fails on kfreebsd-* the context-test [1]
It would be great if porters could have a look.
[1]
https://buildd.debian.org/status/fetch.php?pkg=libsoup2.4&arch=kfreebs
19 matches
Mail list logo
