+1 On Wed, Apr 27, 2016 at 7:38 AM Christopher Shannon < [email protected]> wrote:
> The test failure is not an issue because the test itself is the problem. > It is related to https://issues.apache.org/jira/browse/AMQ-6175 Gary > fixed > the test in master but it wasn't backported to 5.13.x. (I'll do that now in > case o a 5.13.4) > > We have been working gradually on fixing tests with hard coded ports (a lot > have been fixed already) but not all of them have been fixed yet. Some of > the network tests are more tricky to not rely on hard code ports. > > On Tue, Apr 26, 2016 at 5:12 PM, artnaseef <[email protected]> wrote: > > > I keep getting the following test failure on the build: > > > > > > > > > > testSuppression(org.apache.activemq.broker.jmx.SelectiveMBeanRegistrationTest) > > > Time elapsed: 30.616 sec <<< FAILURE! > > > java.lang.AssertionError: one sub > > > at org.junit.Assert.fail(Assert.java:88) > > > at org.junit.Assert.assertTrue(Assert.java:41) > > > at > > > > > > org.apache.activemq.broker.jmx.SelectiveMBeanRegistrationTest.testSuppression(SelectiveMBeanRegistrationTest.java:86) > > > > Any thoughts? > > > > Note that I also had failures on another test because that test > hard-coded > > port numbers that were in-use on my system (that's > > RequestReplyToTopicViaThreeNetworkHopsTest). > > > > > > > > -- > > View this message in context: > > > http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-13-3-tp4711217p4711242.html > > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. > > >
