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 (JIRA)" <ji...@apache.org> on 2011/07/15 12:07:59 UTC
[jira] [Updated] (QPID-3359) FailoverMethodTest.testNoFailover
unreliable since QPID-2815
[ https://issues.apache.org/jira/browse/QPID-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-3359:
-----------------------------
Component/s: Java Tests
Affects Version/s: 0.13
Fix Version/s: 0.13
Assignee: Keith Wall
> FailoverMethodTest.testNoFailover unreliable since QPID-2815
> ------------------------------------------------------------
>
> Key: QPID-3359
> URL: https://issues.apache.org/jira/browse/QPID-3359
> Project: Qpid
> Issue Type: Bug
> Components: Java Tests
> Affects Versions: 0.13
> Reporter: Keith Wall
> Assignee: Keith Wall
> Priority: Minor
> Fix For: 0.13
>
>
> FailoverMethodTest used to be inVM tests until QPID-2815, with removal of ivVM, converted the test to use QpidBrokerTestCase. However, since then we notice this test fails on slower CI boxes. It turns out the test design is *extremely* sensitive the length of time the broker takes to start up. If broker startup is slightly too slow, the test fails, and 'spawn' profiles leave behind a broker process (causing subsequent tests to fail).
> We will make the test a same-VM test to temporarily avoid the issue. In long term, test needs redesigned to avoid the issue.
--
This message is automatically generated by JIRA.
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