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 framing tests > Content-Length larger than message body length > Server claims 'Connection: close' but doesn't > > Unexpected timing out of persistent connections > Async session > First message > Second message > Sync session > First message > Second message > > Exceeding max-conns > Async session > Sync session > > Non-persistent connections are closed immediately > Async session > Sync session > > Non-idempotent methods are always sent on new connections > Async session > Sync session > > connection-test: OK Failure on next attempt: > steven@kfreebsd-i386:~/libsoup2.4-2.38.0$ tests/connection-test -d > > Invalid Content-Length framing tests > Content-Length larger than message body length > Server claims 'Connection: close' but doesn't > > Unexpected timing out of persistent connections > Async session > First message > Second message > Sync session > First message > Second message > > Exceeding max-conns > Async session > Sync session > > Non-persistent connections are closed immediately > Async session > Sync session > leaked SoupSession! > > Non-idempotent methods are always sent on new connections > Async session > > (connection-test:9504): libsoup-CRITICAL **: soup_message_queue_destroy: > assertion `queue->head == NULL' failed > Sync session > > connection-test: 2 error(s). Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
