You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (Commented) (JIRA)" <ji...@apache.org> on 2012/02/10 09:29:59 UTC
[jira] [Commented] (QPID-3824) Additional queue statistics, posix
memory statistics, and broker-scope statistics
[ https://issues.apache.org/jira/browse/QPID-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205289#comment-13205289 ]
Keith Wall commented on QPID-3824:
----------------------------------
Hi
I think this commit broke running of the Python tests on Jenkins for both the C++ and Java Brokers. There is a compilation problem:
https://builds.apache.org//view/M-R/view/Qpid/job/Qpid-Python-Cpp-Test/
https://builds.apache.org//view/M-R/view/Qpid/job/Qpid-Python-Java-Test/
https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Python-Java-Test/ws/trunk/qpid/python/build/results/
The error message:
Traceback (most recent call last):
File "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/trunk/qpid/python/qpid-python-test", line 563, in <module>
m = __import__(name, None, None, ["dummy"])
File "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/trunk/qpid/tests/src/py/qpid_tests/__init__.py", line 22, in <module>
import broker_0_10, broker_0_9, broker_0_8
File "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/trunk/qpid/tests/src/py/qpid_tests/broker_0_10/__init__.py", line 38, in <module>
from stats import *
File "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/trunk/qpid/tests/src/py/qpid_tests/broker_0_10/stats.py", line 30, in <module>
from qpidtoollibs.broker import BrokerAgent
ImportError: No module named qpidtoollibs.broker
> Additional queue statistics, posix memory statistics, and broker-scope statistics
> ---------------------------------------------------------------------------------
>
> Key: QPID-3824
> URL: https://issues.apache.org/jira/browse/QPID-3824
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker, python tools
> Reporter: Ted Ross
> Assignee: Ted Ross
> Fix For: 0.15
>
>
> This feature introduces new counters to the Queue and Broker management objects. The broker counters are aggregate values of all queues in the broker.
> * = Already in the management model
> ||Counter||Queue||Broker||Description||
> |queueCount| |X|The number of queues on the broker|
> |msgTotalEnqueues, byteTotalEnqueues|*|X|Total Enqueues (messages, bytes)|
> |msgTotalDequeues, byteTotalDequeues|*|X|Total Dequeues (messages, bytes) This does not count messages acquired but not completed.|
> |msgDepth, byteDepth|*|X|Total mesages, bytes in the broker|
> |msgPersistEnqueues, bytePersistEnqueues|*|X|Durable messages/bytes enqueued into durable queues|
> |msgPersistDequeues, bytePersistDequeues|*|X|Durable messages/bytes dequeued from durable queues|
> |msgTxnEnqueues, byteTxnEnqueues|*|X|Transactional enqueues in messages/bytes|
> |msgTxnDequeues, byteTxnDequeues|*|X|Transactional dequeues in messages/bytes|
> |msgFtdEnqueues, byteFtdEnqueues|X|X|Messages/bytes flowed to disk (released from memory)|
> |msgFtdDequeues, byteFtdDequeues|X|X|Messages/bytes recovered from disk for consumption|
> |msgFtdDepth, byteFtdDepth|X|X|Messages/bytes currently flowed to disk|
> |releases|X|X|Total messages released from acquired state (explicitly by API or due to subscriber deletion)|
> |acquires|X|X|Total messages acquired|
> |discardsNoRoute| |X|Messages discarded due to no-route from exchange|
> |discardsTtl|X|X|Messages discarded due to TTL expiration|
> |discardsRing|X|X|Messages discarded on full ring queue|
> |discardsLvq|X|X|Messages discarded from LVQ due to key match|
> |discardsOverflow|X|X|Messages discarded due to limit exceeded (sender exception thrown)|
> |discardsSubscriber|X|X|Messages rejected by subscriber|
> |discardsPurge|X|X|Messages purged by management request|
> |reroutes|X|X|Messages rerouted by management request|
> |abandoned| |X|Messages abandoned in deleted queues|
> |abandonedViaAlt| |X|Messages routed to alternate exchange in deleted queues|
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: [jira] [Commented] (QPID-3824) Additional queue statistics, posix
memory statistics, and broker-scope statistics
Posted by Keith W <ke...@gmail.com>.
Hi Ted
> It looks like this test runs out of the svn tree (as opposed to installed).
Jenkins uses an Ant wrapper python/qpid-python-test-ant.xml around
qpid-python-test. It does run the tests straight from the svn as
opposed to the installed. I set this up, and didn't realise there was
another approach (how would I do it?).
> There is a need for an environment variable in the test environment.
It already sets PYTHONPATH to
${qpid.root.dir}/tests/src/py:${qpid.root.dir}/extras/qmf/src/py, is
there now something else?
> I'm logged into Jenkins but I can't find a page for test configuration.
I *think* you need to permissioned separately for configuration access
to Jenkins. If you have the permission, there is a Configure link on
the LHS after you've clicked through to the Jenkins job.
cheers, Keith.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: [jira] [Commented] (QPID-3824) Additional queue statistics, posix
memory statistics, and broker-scope statistics
Posted by Ted Ross <tr...@redhat.com>.
It looks like this test runs out of the svn tree (as opposed to
installed). There is a need for an environment variable in the test
environment. Can someone point me to where the Jenkins tests are
configured? I'm logged into Jenkins but I can't find a page for test
configuration.
Thanks,
-Ted
On 02/10/2012 03:29 AM, Keith Wall (Commented) (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/QPID-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205289#comment-13205289 ]
>
> Keith Wall commented on QPID-3824:
> ----------------------------------
>
> Hi
>
> I think this commit broke running of the Python tests on Jenkins for both the C++ and Java Brokers. There is a compilation problem:
>
> https://builds.apache.org//view/M-R/view/Qpid/job/Qpid-Python-Cpp-Test/
> https://builds.apache.org//view/M-R/view/Qpid/job/Qpid-Python-Java-Test/
>
>
> https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Python-Java-Test/ws/trunk/qpid/python/build/results/
>
>
> The error message:
>
>
> Traceback (most recent call last):
> File "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/trunk/qpid/python/qpid-python-test", line 563, in<module>
> m = __import__(name, None, None, ["dummy"])
> File "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/trunk/qpid/tests/src/py/qpid_tests/__init__.py", line 22, in<module>
> import broker_0_10, broker_0_9, broker_0_8
> File "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/trunk/qpid/tests/src/py/qpid_tests/broker_0_10/__init__.py", line 38, in<module>
> from stats import *
> File "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/trunk/qpid/tests/src/py/qpid_tests/broker_0_10/stats.py", line 30, in<module>
> from qpidtoollibs.broker import BrokerAgent
> ImportError: No module named qpidtoollibs.broker
>
>
>> Additional queue statistics, posix memory statistics, and broker-scope statistics
>> ---------------------------------------------------------------------------------
>>
>> Key: QPID-3824
>> URL: https://issues.apache.org/jira/browse/QPID-3824
>> Project: Qpid
>> Issue Type: Improvement
>> Components: C++ Broker, python tools
>> Reporter: Ted Ross
>> Assignee: Ted Ross
>> Fix For: 0.15
>>
>>
>> This feature introduces new counters to the Queue and Broker management objects. The broker counters are aggregate values of all queues in the broker.
>> * = Already in the management model
>> ||Counter||Queue||Broker||Description||
>> |queueCount| |X|The number of queues on the broker|
>> |msgTotalEnqueues, byteTotalEnqueues|*|X|Total Enqueues (messages, bytes)|
>> |msgTotalDequeues, byteTotalDequeues|*|X|Total Dequeues (messages, bytes) This does not count messages acquired but not completed.|
>> |msgDepth, byteDepth|*|X|Total mesages, bytes in the broker|
>> |msgPersistEnqueues, bytePersistEnqueues|*|X|Durable messages/bytes enqueued into durable queues|
>> |msgPersistDequeues, bytePersistDequeues|*|X|Durable messages/bytes dequeued from durable queues|
>> |msgTxnEnqueues, byteTxnEnqueues|*|X|Transactional enqueues in messages/bytes|
>> |msgTxnDequeues, byteTxnDequeues|*|X|Transactional dequeues in messages/bytes|
>> |msgFtdEnqueues, byteFtdEnqueues|X|X|Messages/bytes flowed to disk (released from memory)|
>> |msgFtdDequeues, byteFtdDequeues|X|X|Messages/bytes recovered from disk for consumption|
>> |msgFtdDepth, byteFtdDepth|X|X|Messages/bytes currently flowed to disk|
>> |releases|X|X|Total messages released from acquired state (explicitly by API or due to subscriber deletion)|
>> |acquires|X|X|Total messages acquired|
>> |discardsNoRoute| |X|Messages discarded due to no-route from exchange|
>> |discardsTtl|X|X|Messages discarded due to TTL expiration|
>> |discardsRing|X|X|Messages discarded on full ring queue|
>> |discardsLvq|X|X|Messages discarded from LVQ due to key match|
>> |discardsOverflow|X|X|Messages discarded due to limit exceeded (sender exception thrown)|
>> |discardsSubscriber|X|X|Messages rejected by subscriber|
>> |discardsPurge|X|X|Messages purged by management request|
>> |reroutes|X|X|Messages rerouted by management request|
>> |abandoned| |X|Messages abandoned in deleted queues|
>> |abandonedViaAlt| |X|Messages routed to alternate exchange in deleted queues|
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org