On 04/29/2010 02:44 PM, Ján Sáreník wrote:
Hi again!

On Thu, Apr 29, 2010 at 07:56:02PM +0200, Ján Sáreník wrote:
There are only Valgrind errors that I see and Gordon says they are
merely SASL-related. Should I send a bug-report to cyrus-sasl to make
it clean or should those error be added as exceptions? I would like to
spread the word about qpid and to encourage people from community to
compile it and give it a try. If some of them have valgrind installed
they could be surprised that the tests fail...

What OS & versions (incl. cyrus-sasl version) are you seeing this on? We should check if these are really cyrus bugs, if so ignore them, or if qpid is not doing its part to clean up some memory allocated by cyrus.

After more 'make check's even with "VALGRIND=" to disable it,
I got few different errors:

  1. https://issues.apache.org/jira/browse/QPID-2552 reported earlier
     (just to prove it is still valid)

  2. cluster_read_credit fails randomly as well
     I thought I worked this error around by making sure there
     are no leftover pidfiles in ~/.qpidd or /tmp and no leftover
     daemons running, but it does not help actually. It says:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
PASS: run_cluster_test
2010-04-29 20:27:17 warning Connection closed
2010-04-29 20:27:17 warning Connect failed: Connection refused
2010-04-29 20:27:17 warning Connection closed
Failed: Cannot establish a connection
2010-04-29 20:27:17 critical Unexpected error: Removing stale lock file 
/tmp/qpidd.46939.pid
Errors stopping brokers on ports:  46939
FAIL: cluster_read_credit
PASS: test_watchdog
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Alan, you have a log entry for cluster_read_credit file, do you
have an idea how to fix it?


Please create a JIRA with this info and assign it to me, I'll look into it.

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to