You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joe Skora (JIRA)" <ji...@apache.org> on 2016/09/12 17:18:20 UTC

[jira] [Created] (NIFI-2759) TestListDatabaseTables.testListTablesMultipleRefresh consistently failing

Joe Skora created NIFI-2759:
-------------------------------

             Summary: TestListDatabaseTables.testListTablesMultipleRefresh consistently failing
                 Key: NIFI-2759
                 URL: https://issues.apache.org/jira/browse/NIFI-2759
             Project: Apache NiFi
          Issue Type: Bug
          Components: Core Framework
    Affects Versions: 1.0.0
            Reporter: Joe Skora
            Priority: Critical


Running this test repeatedly produces errors.

{code}
Running org.apache.nifi.processors.standard.TestListDatabaseTables
Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 13.114 sec <<< FAILURE! - in org.apache.nifi.processors.standard.TestListDatabaseTables
testListTablesMultipleRefresh(org.apache.nifi.processors.standard.TestListDatabaseTables)  Time elapsed: 0.794 sec  <<< FAILURE!
java.lang.AssertionError: expected:<1> but was:<2>
        at org.junit.Assert.fail(Assert.java:88)
        at org.junit.Assert.failNotEquals(Assert.java:834)
        at org.junit.Assert.assertEquals(Assert.java:645)
        at org.junit.Assert.assertEquals(Assert.java:631)
        at org.apache.nifi.util.StandardProcessorTestRunner.assertTransferCount(StandardProcessorTestRunner.java:318)
        at org.apache.nifi.processors.standard.TestListDatabaseTables.testListTablesMultipleRefresh(TestListDatabaseTables.java:216)
{code}

followed by 

{code}
Failed tests:
  TestListDatabaseTables.testListTablesMultipleRefresh:216 expected:<1> but was:<2>
{code}

I tried removing the [runner.clearTransferState();|https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/test/java/org/apache/nifi/processors/standard/TestListDatabaseTables.java#L210] thinking the reset was causing both tables to show but that did not make a difference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)