[
https://issues.apache.org/jira/browse/QPIDJMS-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599464#comment-14599464
]
Robbie Gemmell commented on QPIDJMS-76:
---------------------------------------
While trying to debug this remotely using a Jenkins job I found that the tests
passed on certain nodes they had failed on previously, but failed again at
other times.
I hacked in some code updates directly on the node to try and determine what
was going on, and after getting some matching passing and failing logs I could
see that there were additional network interfaces available at the time due to
use of docker, and different interfaces were being selected by the tests/client
and broker. This was letting the pre-test JUnit assumption check pass but
resulting in the test failing despite that, due to client and broker defaulting
to using disjoint interfaces.
QPIDJMS-77 updated the default interface selection on the client to align
better with what the released brokers do, and added some additional logging to
make it easier to figure out what it is doing. I also changed the tests via
this original JIRA to configure the broker to use the same interface as the
assumption check did. Either of those changes resulted in the tests passing on
the affected nodes.
> multicast discovery tests fail 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]
