qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ján Sáreník <jsare...@redhat.com>
Subject check-long failures on Rawhide
Date Thu, 15 Apr 2010 17:15:45 GMT
  Hello!

On Fedora Rawhide, qpid r934287. I simply did:

  cd qpid
  patch -Np1 < qpid-r934287.patch # see attachment
  cd cpp
  ./bootstrap
  ./configure --disable-static --with-cpg \
    CXXFLAGS="$CXXFLAGS -DNDEBUG -O3"
  make -j5
  make check
  make check-long

I did
  :%s/2010-..-.. ..:..:.. //
in Vim to send only the relevant content (the timing is not problem here).
And here are the significant parts of check-long:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
make[2]: Leaving directory `/mnt/virtual/jasan/pub/git/qpid/cpp/src/tests'
make  check-TESTS
make[2]: Entering directory `/mnt/virtual/jasan/pub/git/qpid/cpp/src/tests'
/home/jsarenik/pub/git/qpid/cpp/src/tests/python/qpid/brokertest.py:23: DeprecationWarning:
The popen2 module is deprecated.  Use the subprocess module.
  import os, signal, string, tempfile, popen2, socket, threading, time, imp, re
cluster_tests.LongTests.test_failover ................................... pass
cluster_tests.LongTests.test_management ................................. fail
Error during test:
  Traceback (most recent call last):
    File "/home/jsarenik/pub/git/qpid/cpp/src/tests/python/commands/qpid-python-test", line
311, in run
      phase()
    File "/home/jsarenik/pub/git/qpid/cpp/src/tests/cluster_tests.py", line 245, in test_management
      cluster.start()
    File "/home/jsarenik/pub/git/qpid/cpp/src/tests/python/qpid/brokertest.py", line 412,
in start
      self._brokers.append(self.test.broker(self.args+args, name, expect, wait, port=port))
    File "/home/jsarenik/pub/git/qpid/cpp/src/tests/python/qpid/brokertest.py", line 475,
in broker
      raise Exception("Failed to start broker %s(%s): %s" % (b.name, b.log, e))
  Exception: Failed to start broker cluster1-5(cluster1-5.log): Broker cluster1-5 failed ready
test
  Traceback (most recent call last):
    File "/home/jsarenik/pub/git/qpid/cpp/src/tests/python/qpid/brokertest.py", line 381,
in ready
      try: self.connect().close()
    File "/home/jsarenik/pub/git/qpid/cpp/src/tests/python/qpid/brokertest.py", line 306,
in connect
      port=self.port())
    File "/home/jsarenik/pub/git/qpid/cpp/src/tests/python/qpid/messaging/endpoints.py", line
60, in establish
      conn.open()
    File "<string>", line 6, in open
    File "/home/jsarenik/pub/git/qpid/cpp/src/tests/python/qpid/messaging/endpoints.py", line
227, in open
      self.attach()
    File "<string>", line 6, in attach
    File "/home/jsarenik/pub/git/qpid/cpp/src/tests/python/qpid/messaging/endpoints.py", line
244, in attach
      self._ewait(lambda: self._transport_connected and not self._unlinked())
    File "/home/jsarenik/pub/git/qpid/cpp/src/tests/python/qpid/messaging/endpoints.py", line
185, in _ewait
      self.check_error()
    File "/home/jsarenik/pub/git/qpid/cpp/src/tests/python/qpid/messaging/endpoints.py", line
178, in check_error
      raise self.error
  ConnectError: [Errno 111] Connection refused
Totals: 12 tests, 1 passed, 0 skipped, 10 ignored, 1 failed
FAIL: run_long_cluster_tests
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


Other shortly follow
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
warning Connecting failed: Connection refused
warning Connection closed

Connection closed
FAIL: multiq_perftest
warning Connecting failed: Connection refused
warning Connection closed

Connection closed
FAIL: topic_perftest
[Errno 111] Connection refused
Starting 4 senders concurrently with 4 receivers
warning Connecting failed: Connection refused
warning Connection closed
warning Connecting failed: Connection refused
warning Connection closed
Failed: Cannot establish a connection
Failed: Cannot establish a connection
warning Connecting failed: Connection refused
warning Connection closed
Failed: Cannot establish a connection
warning Connecting failed: Connection refused
warning Connection closed
Failed: Cannot establish a connection
warning Connecting failed: Connection refused
warning Connection closed
Failure: Cannot establish a connection
warning Connecting failed: Connection refused
warning Connection closed
Failure: Cannot establish a connection
warning Connecting failed: Connection refused
warning Connection closed
warning Connecting failed: Connection refused
warning Connection closed
Failure: Cannot establish a connection
Failure: Cannot establish a connection
warning Connecting failed: Connection refused
warning Connection closed
Failed: Cannot establish a connection
sent at least as many messages as were received
[Errno 111] Connection refused
[Errno 111] Connection refused
Starting 4 senders followed by 0 receivers 
warning Connecting failed: Connection refused
warning Connection closed
Failed: Cannot establish a connection
warning Connecting failed: Connection refused
warning Connection closed
Failed: Cannot establish a connection
warning Connecting failed: Connection refused
warning Connection closed
Failed: Cannot establish a connection
warning Connecting failed: Connection refused
warning Connection closed
Failed: Cannot establish a connection
warning Connecting failed: Connection refused
warning Connection closed
Failed: Cannot establish a connection
warning Connecting failed: Connection refused
warning Connection closed
Failure: Cannot establish a connection
queue does not contain the expected 100 messages (received 0)
ring_queue_test: FAILED
[Errno 111] Connection refused
Starting 1 senders followed by 1 receivers 
warning Connecting failed: Connection refused
warning Connection closed
Failed: Cannot establish a connection
warning Connecting failed: Connection refused
warning Connection closed
Failed: Cannot establish a connection
warning Connecting failed: Connection refused
warning Connection closed
Failure: Cannot establish a connection
received 0 messages, expected 99
did not receive expected messages
ring_queue_test: FAILED
FAIL: run_ring_queue_test
critical Unexpected error: Removing stale lock file /home/jsarenik/.qpidd/qpidd.35223.pid
FAIL: stop_broker
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                              ^^^^^^^^^^^^^^^^^^^^^^^^^^- see few lines above
I am sure there was no ~/.qpidd when I started the tests.
The tests should be rewritten to use their own --data-dir
which is clean in the beginning.

Failover soak went fine.

So the result is
====================================
5 of 14 tests failed
Please report to dev@qpid.apache.org
====================================

 HTH and get back to me if you need more info
  Best regards, Ján

fedora-release-14-0.4.noarch
corosynclib-devel-1.2.1-1.fc14.x86_64
boost-devel-1.41.0-8.fc14.x86_64
cyrus-sasl-md5-2.1.23-12.fc14.x86_64
cyrus-sasl-devel-2.1.23-12.fc14.x86_64
cyrus-sasl-plain-2.1.23-12.fc14.x86_64
cyrus-sasl-lib-2.1.23-12.fc14.x86_64
cyrus-sasl-2.1.23-12.fc14.x86_64
cyrus-sasl-gssapi-2.1.23-12.fc14.x86_64

-- 
Red Hat Czech, MRG Quality Engineering

Mime
View raw message