ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-6667) Unit test failures on jenkins for Ambari 1.7.0 related to alerts.
Date Wed, 30 Jul 2014 04:42:39 GMT
Jonathan Hurley created AMBARI-6667:
---------------------------------------

             Summary: Unit test failures on jenkins for Ambari 1.7.0 related to alerts.
                 Key: AMBARI-6667
                 URL: https://issues.apache.org/jira/browse/AMBARI-6667
             Project: Ambari
          Issue Type: Bug
    Affects Versions: 1.7.0
            Reporter: Jonathan Hurley
            Assignee: Jonathan Hurley
            Priority: Critical
             Fix For: 1.7.0


Tests run locally and pass 100% consistently.
These test results are fishy; they randomly fail on different OS deployments. Even the simple
logic ones fail. There are only 5 alert targets ever created, yet there are 9 returned sometimes.
I'm wondering if this is because we tried to load some data in the @BeforeClass instead of
@Before - maybe there's a weird Guice/JUnit race condition going on.
I can't say I can fix this with confidence since I can't reproduce it. I'm going to move some
things to @Before and hope it helps.

{code}
java.lang.AssertionError: expected:<5> but was:<9>
	at org.junit.Assert.fail(Assert.java:93)
	at org.junit.Assert.failNotEquals(Assert.java:647)
	at org.junit.Assert.assertEquals(Assert.java:128)
	at org.junit.Assert.assertEquals(Assert.java:472)
	at org.junit.Assert.assertEquals(Assert.java:456)
	at org.apache.ambari.server.orm.dao.AlertDispatchDAOTest.testFindAllTargets(AlertDispatchDAOTest.java:117)
{code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message