Gardella Juan Pablo created NIFI-9225:
-----------------------------------------

             Summary: Some JMS unit tests are failing since nifi 1.14.0
                 Key: NIFI-9225
                 URL: https://issues.apache.org/jira/browse/NIFI-9225
             Project: Apache NiFi
          Issue Type: Bug
          Components: Core Framework
    Affects Versions: 1.14.0
            Reporter: Gardella Juan Pablo



[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.apache.nifi.jms.cf.JMSConnectionFactoryProviderTest
[INFO] Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.636 s 
- in org.apache.nifi.jms.cf.JMSConnectionFactoryProviderTest
[INFO] Running org.apache.nifi.jms.processors.JMSPublisherConsumerTest
[ERROR] Tests run: 10, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 21.21 
s <<< FAILURE! - in org.apache.nifi.jms.processors.JMSPublisherConsumerTest
[ERROR] 
validateMessageRedeliveryWhenNotAcked(org.apache.nifi.jms.processors.JMSPublisherConsumerTest)
  Time elapsed: 0.038 s  <<< FAILURE!
org.junit.ComparisonFailure: expected:<[2]> but was:<[1]>
        at 
org.apache.nifi.jms.processors.JMSPublisherConsumerTest.validateMessageRedeliveryWhenNotAcked(JMSPublisherConsumerTest.java:458)

[ERROR] 
testMultipleThreads(org.apache.nifi.jms.processors.JMSPublisherConsumerTest)  
Time elapsed: 20.003 s  <<< ERROR!
org.junit.runners.model.TestTimedOutException: test timed out after 20000 
milliseconds
        at 
app//org.apache.nifi.jms.processors.JMSPublisherConsumerTest.testMultipleThreads(JMSPublisherConsumerTest.java:374)
Nifi 1.14.0 by renaming JMSPublisherConsumerTest to be covered by mvn test 
command.

Nifi 1.13.2 success 

[INFO] --- maven-surefire-plugin:2.22.2:test (default-test) @ 
nifi-jms-processors ---
[INFO] 
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.apache.nifi.jms.cf.JMSConnectionFactoryProviderTest
[INFO] Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.512 s 
- in org.apache.nifi.jms.cf.JMSConnectionFactoryProviderTest
[INFO] Running org.apache.nifi.jms.processors.JMSPublisherConsumerTest
[INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.781 s 
- in org.apache.nifi.jms.processors.JMSPublisherConsumerTest
[INFO] Running org.apache.nifi.jms.processors.ConsumeJMSManualTest
[WARNING] Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0 s - 
in org.apache.nifi.jms.processors.ConsumeJMSManualTest
[INFO] Running 
org.apache.nifi.jms.processors.ConnectionFactoryConfigValidatorTest
[INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.022 s 
- in org.apache.nifi.jms.processors.ConnectionFactoryConfigValidatorTest
[INFO] 
[INFO] Results:

Be aware that JMS is not safe to be used in Nifi 1.14.0 (at least by looking at 
unit tests.) 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to