[
https://issues.apache.org/jira/browse/QPIDJMS-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14601332#comment-14601332
]
ASF subversion and git services commented on QPIDJMS-76:
--------------------------------------------------------
Commit e0a49ba179df5fe21aaf6cb222f3bab1434661de in qpid-jms's branch
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=e0a49ba ]
QPIDJMS-76: do the multicast assumption check before trying to start the
broker, avoids hitting cases where doing so actually fails
> multicast discovery tests fail sporadically on some of the Jenkins CI nodes
> ---------------------------------------------------------------------------
>
> Key: QPIDJMS-76
> URL: https://issues.apache.org/jira/browse/QPIDJMS-76
> Project: Qpid JMS
> Issue Type: Task
> Components: qpid-jms-discovery
> Affects Versions: 0.4.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
>
> The multicast discovery tests fail to work on some of the Jenkins 'Ubuntu'
> label nodes, but succeed on others.
> The tests have a pre-run JUnit assumption validation that verifies multicast
> is operational, and skips the test if is not in order to avoid failing on
> systems with firewalls etc. This verification is succeeding which allows the
> tests run, but they then fail as the running ActiveMQ broker doesn't get
> discovered and the connection attempt fails after exhausting its retry limit.
> The assumption verification either needs updating, or the tests configured
> differently, to make the tests pass or skip if they can't be run successfully
> in the particular nodes environment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
