You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2015/06/24 16:13:05 UTC
[jira] [Updated] (QPIDJMS-76) multicast discovery tests fail
sporadically on some of the Jenkins CI nodes
[ https://issues.apache.org/jira/browse/QPIDJMS-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPIDJMS-76:
----------------------------------
Summary: multicast discovery tests fail sporadically on some of the Jenkins CI nodes (was: multicast discovery tests fail on some of the Jenkins CI nodes)
> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org