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 (Updated) (JIRA)" <ji...@apache.org> on 2012/01/18 09:33:40 UTC
[jira] [Updated] (QPID-3768) Test
org.apache.qpid.server.queue.SortedQueueTest.testGetNextWithAck fails
sporadically on CI
[ https://issues.apache.org/jira/browse/QPID-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-3768:
-----------------------------
Description:
test profile:java-mms-spawn.0-9-1
Received message with unexpected sorted key value expected:<7> but was:<6>
{code}
Stacktrace
junit.framework.ComparisonFailure: Received message with unexpected sorted key value expected:<7> but was:<6>
at org.apache.qpid.server.queue.SortedQueueTest.receiveAndValidateMessage(SortedQueueTest.java:352)
at org.apache.qpid.server.queue.SortedQueueTest.testGetNextWithAck(SortedQueueTest.java:300)
at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:240)
at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:135)
{code}
was:
test profile:java-mms-spawn.0-9-1
Received message with unexpected sorted key value expected:<7> but was:<6>Stacktrace
junit.framework.ComparisonFailure: Received message with unexpected sorted key value expected:<7> but was:<6>
at org.apache.qpid.server.queue.SortedQueueTest.receiveAndValidateMessage(SortedQueueTest.java:352)
at org.apache.qpid.server.queue.SortedQueueTest.testGetNextWithAck(SortedQueueTest.java:300)
at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:240)
at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:135)
This test occasionally fails because it assumes that as messages 7, 6 and 5 are sent in individual transactions (SortedQueueTest.java,295-297) they will be delivered immediately to the client and not be subject to sorting by the queue. This assumption is unsafe.
When the test fails (SortedQueueTest.java, 300) messages 7 and 6 have resided momentarily together in the queue and therefore have been sorted. The test sees message 6 when it expects message 7.
The test needs to be changed to avoid assuming that the assertion on line 300 will always see message 7 and could in fact see message 6 or even 5.
> Test org.apache.qpid.server.queue.SortedQueueTest.testGetNextWithAck fails sporadically on CI
> ---------------------------------------------------------------------------------------------
>
> Key: QPID-3768
> URL: https://issues.apache.org/jira/browse/QPID-3768
> Project: Qpid
> Issue Type: Bug
> Components: Java Tests
> Affects Versions: 0.15
> Reporter: Keith Wall
> Assignee: Keith Wall
> Priority: Minor
>
> test profile:java-mms-spawn.0-9-1
> Received message with unexpected sorted key value expected:<7> but was:<6>
> {code}
> Stacktrace
> junit.framework.ComparisonFailure: Received message with unexpected sorted key value expected:<7> but was:<6>
> at org.apache.qpid.server.queue.SortedQueueTest.receiveAndValidateMessage(SortedQueueTest.java:352)
> at org.apache.qpid.server.queue.SortedQueueTest.testGetNextWithAck(SortedQueueTest.java:300)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:240)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:135)
> {code}
--
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