[jira] [Updated] (OOZIE-3235) Upgrade ActiveMQ to 5.15.3

[Andras Piros (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Piros updated OOZIE-3235:

Summary: Upgrade ActiveMQ to 5.15.3  (was: Upgrade Old ActiveMQ dependency 
in Oozie)

> Upgrade ActiveMQ to 5.15.3
> --
>
> Key: OOZIE-3235
> URL: https://issues.apache.org/jira/browse/OOZIE-3235
> Project: Oozie
>  Issue Type: Bug
>  Components: client
>Affects Versions: 5.1.0
>Reporter: Mate Juhasz
>Assignee: Mate Juhasz
>Priority: Minor
> Fix For: 5.1.0
>
> Attachments: OOZIE-3235-001.patch, OOZIE-3235-002.patch
>
>
> An old, and vulnerable version of ActiveMQ is used by Oozie's tests (5.13.3).
> It seems that the jars are even included in the oozie-client with "compile" 
> scope, but we only use them in unit tests.
> Oozie-client uses the JMS-API only from these jars, which could be included 
> separately (javax.jms).
> The version could be upgraded to 5.14.2 and the scope changed to "test" 
> instead of "compile".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 67112: OOZIE-3228 [Spark action] Can't load properties from spark-defaults.conf

[András Piros via Review Board]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/67112/
---

(Updated May 16, 2018, 9:23 a.m.)


Review request for oozie and Peter Cseh.


Repository: oozie-git


Description
---

OOZIE-3228 [Spark action] Can't load properties from spark-defaults.conf


Diffs (updated)
-

  
sharelib/spark/src/main/java/org/apache/oozie/action/hadoop/SparkArgsExtractor.java
 5af39cda52b403d8989fdd5d4f2524395a55580a 
  
sharelib/spark/src/test/java/org/apache/oozie/action/hadoop/TestSparkArgsExtractor.java
 6a9baa5c7997198ab69f039f6a8884e49b13cad3 


Diff: https://reviews.apache.org/r/67112/diff/3/

Changes: https://reviews.apache.org/r/67112/diff/2-3/


Testing
---

`mvn clean test -Dtest=TestSparkArgsExtractor`


Thanks,

András Piros

[jira] [Updated] (OOZIE-3228) [Spark action] Can't load properties from spark-defaults.conf

[Andras Piros (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Piros updated OOZIE-3228:

Attachment: OOZIE-3228.004.patch

> [Spark action] Can't load properties from spark-defaults.conf
> -
>
> Key: OOZIE-3228
> URL: https://issues.apache.org/jira/browse/OOZIE-3228
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Tang Yan
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3228.001.patch, OOZIE-3228.002.patch, 
> OOZIE-3228.003.patch, OOZIE-3228.004.patch
>
>
> When I create a Oozie workflow to launch a spark action, the spark job can't 
> load the configured properties in {{spark-defaults.conf}}. I've configured 
> each NodeManager as the Spark gateway role, so {{spark-defaults.conf}} is 
> generated in {{/etc/spark/conf/}} on each worker node.
> In {{spark-defaults.conf}} some configuration I've set into.
> {noformat}
> spark.executor.extraClassPath=/etc/hbase/conf:/etc/hive/conf
> spark.driver.extraClassPath=/etc/hbase/conf:/etc/hive/conf
> {noformat}
> But in the Oozie spark job, they're not loaded automatically.
> {noformat}
> --conf spark.executor.extraClassPath=$PWD/*
> --conf spark.driver.extraClassPath=$PWD/*
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3228) [Spark action] Can't load properties from spark-defaults.conf

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477157#comment-16477157
 ] 

Hadoop QA commented on OOZIE-3228:
--

PreCommit-OOZIE-Build started


> [Spark action] Can't load properties from spark-defaults.conf
> -
>
> Key: OOZIE-3228
> URL: https://issues.apache.org/jira/browse/OOZIE-3228
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Tang Yan
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3228.001.patch, OOZIE-3228.002.patch, 
> OOZIE-3228.003.patch, OOZIE-3228.004.patch
>
>
> When I create a Oozie workflow to launch a spark action, the spark job can't 
> load the configured properties in {{spark-defaults.conf}}. I've configured 
> each NodeManager as the Spark gateway role, so {{spark-defaults.conf}} is 
> generated in {{/etc/spark/conf/}} on each worker node.
> In {{spark-defaults.conf}} some configuration I've set into.
> {noformat}
> spark.executor.extraClassPath=/etc/hbase/conf:/etc/hive/conf
> spark.driver.extraClassPath=/etc/hbase/conf:/etc/hive/conf
> {noformat}
> But in the Oozie spark job, they're not loaded automatically.
> {noformat}
> --conf spark.executor.extraClassPath=$PWD/*
> --conf spark.driver.extraClassPath=$PWD/*
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3250) Reduce heap waste by reducing duplicate byte[] count

[Andras Piros (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Piros updated OOZIE-3250:

Attachment: OOZIE-3250.006.patch

> Reduce heap waste by reducing duplicate byte[] count
> 
>
> Key: OOZIE-3250
> URL: https://issues.apache.org/jira/browse/OOZIE-3250
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3250.001.patch, OOZIE-3250.002.patch, 
> OOZIE-3250.003.patch, OOZIE-3250.004.patch, OOZIE-3250.005.patch, 
> OOZIE-3250.006.patch
>
>
> Similar to OOZIE-3232, we also need to intern the {{byte[]}} field values 
> within 
> [*{{BinaryBlob}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/BinaryBlob.java#L32-L33]
>  and 
> [*{{StringBlob}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/StringBlob.java#L34]
>  to reduce heap waste caused by duplicate {{byte[]}} entries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3250) Reduce heap waste by reducing duplicate byte[] count

[Andras Piros (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477192#comment-16477192
 ] 

Andras Piros commented on OOZIE-3250:
-

Thanks for the reviews [~gezapeti] [~mi...@cloudera.com]! Renamed to 
{{ByteArrayUtils}}, and extended Javadoc by mentioning the performance numbers 
from patch 004.

> Reduce heap waste by reducing duplicate byte[] count
> 
>
> Key: OOZIE-3250
> URL: https://issues.apache.org/jira/browse/OOZIE-3250
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3250.001.patch, OOZIE-3250.002.patch, 
> OOZIE-3250.003.patch, OOZIE-3250.004.patch, OOZIE-3250.005.patch, 
> OOZIE-3250.006.patch
>
>
> Similar to OOZIE-3232, we also need to intern the {{byte[]}} field values 
> within 
> [*{{BinaryBlob}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/BinaryBlob.java#L32-L33]
>  and 
> [*{{StringBlob}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/StringBlob.java#L34]
>  to reduce heap waste caused by duplicate {{byte[]}} entries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3236) Flaky test TestHiveActionExecutor#testHiveAction

[Peter Bacsko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Bacsko updated OOZIE-3236:

Attachment: OOZIE-3236-001.patch

> Flaky test TestHiveActionExecutor#testHiveAction
> 
>
> Key: OOZIE-3236
> URL: https://issues.apache.org/jira/browse/OOZIE-3236
> Project: Oozie
>  Issue Type: Sub-task
>  Components: action, tests
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3236-001.patch, OOZIE-3236.txt
>
>
> The test TestHiveActionExecutor#testHiveAction failed with this error:
> {noformat}
> junit.framework.AssertionFailedError: YARN App state for app 
> application_1525471867439_0002 expected: but was:
>   at 
> org.apache.oozie.action.hadoop.TestHiveActionExecutor.testHiveAction(TestHiveActionExecutor.java:158)
> {noformat}
> https://builds.apache.org/job/PreCommit-OOZIE-Build/516/testReport/junit/org.apache.oozie.action.hadoop/TestHiveActionExecutor/testHiveAction/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 67112: OOZIE-3228 [Spark action] Can't load properties from spark-defaults.conf

[Peter Cseh via Review Board]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/67112/#review203207
---




sharelib/spark/src/main/java/org/apache/oozie/action/hadoop/SparkArgsExtractor.java
Lines 379-398 (patched)


Can you also add this on the twiki level? Most users don't check the source 
code if something happens they don't expect.


- Peter Cseh


On May 16, 2018, 9:23 a.m., András Piros wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67112/
> ---
> 
> (Updated May 16, 2018, 9:23 a.m.)
> 
> 
> Review request for oozie and Peter Cseh.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-3228 [Spark action] Can't load properties from spark-defaults.conf
> 
> 
> Diffs
> -
> 
>   
> sharelib/spark/src/main/java/org/apache/oozie/action/hadoop/SparkArgsExtractor.java
>  5af39cda52b403d8989fdd5d4f2524395a55580a 
>   
> sharelib/spark/src/test/java/org/apache/oozie/action/hadoop/TestSparkArgsExtractor.java
>  6a9baa5c7997198ab69f039f6a8884e49b13cad3 
> 
> 
> Diff: https://reviews.apache.org/r/67112/diff/3/
> 
> 
> Testing
> ---
> 
> `mvn clean test -Dtest=TestSparkArgsExtractor`
> 
> 
> Thanks,
> 
> András Piros
> 
>

[jira] [Updated] (OOZIE-3246) Flaky test TestJMSJobEventListener#testConnectionDrop

[Peter Bacsko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Bacsko updated OOZIE-3246:

Attachment: OOZIE-3246-001.patch

> Flaky test TestJMSJobEventListener#testConnectionDrop
> -
>
> Key: OOZIE-3246
> URL: https://issues.apache.org/jira/browse/OOZIE-3246
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3246-001.patch
>
>
> The testcase TestJMSJobEventListener#testConnectionDrop occasionally fails 
> with the following error:
> {noformat}
> junit.framework.AssertionFailedError: 
> org.apache.activemq:type=Broker,brokerName=localhost
>   at 
> org.apache.oozie.jms.TestJMSJobEventListener.testConnectionDrop(TestJMSJobEventListener.java:365)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3240) Flaky test TestJMSAccessorService#testConnectionRetry

[Peter Bacsko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Bacsko updated OOZIE-3240:

Attachment: OOZIE-3240-002.patch

> Flaky test TestJMSAccessorService#testConnectionRetry
> -
>
> Key: OOZIE-3240
> URL: https://issues.apache.org/jira/browse/OOZIE-3240
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3240-002.patch, OOZIE-3240.txt
>
>
> The test TestJMSAccessorService#testConnectionRetry failed with the following 
> errors in the log:
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.oozie.service.TestJMSAccessorService.testConnectionRetry(TestJMSAccessorService.java:183)
> {noformat}
> {noformat}
> [jndiProperties=java.naming.factory.initial#org.apache.activemq.jndi.ActiveMQInitialContextFactory;java.naming.provider.url#tcp://localhost:39362;connectionFactoryNames#ConnectionFactory]]
> javax.jms.JMSException: Could not connect to broker URL: 
> tcp://localhost:39362. Reason: java.net.ConnectException: Connection refused 
> (Connection refused)
>   at 
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:36)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:373)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:303)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:243)
>   at 
> org.apache.oozie.jms.DefaultConnectionContext.createConnection(DefaultConnectionContext.java:53)
>   at 
> org.apache.oozie.service.JMSAccessorService.createConnectionContext(JMSAccessorService.java:264)
>   at 
> org.apache.oozie.service.JMSAccessorService.registerForNotification(JMSAccessorService.java:110)
>   at 
> org.apache.oozie.service.TestJMSAccessorService.testConnectionRetry(TestJMSAccessorService.java:173)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:255)
>   at junit.framework.TestSuite.run(TestSuite.java:250)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at 
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:410)
>   at 
> org.apache.maven.surefire.junitcore.pc.InvokerStrategy.schedule(InvokerStrategy.java:54)
>   at 
> org.apache.maven.surefire.junitcore.pc.Scheduler.schedule(Scheduler.java:367)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at 
> org.apache.maven.surefire.junitcore.pc.ParallelComputerBuilder$PC$1.run(ParallelComputerBuilder.java:593)
>   at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
>   at 
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
>   at 
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
>   at 
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrappe

[jira] [Commented] (OOZIE-3240) Flaky test TestJMSAccessorService#testConnectionRetry

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477197#comment-16477197
 ] 

Hadoop QA commented on OOZIE-3240:
--

PreCommit-OOZIE-Build started


> Flaky test TestJMSAccessorService#testConnectionRetry
> -
>
> Key: OOZIE-3240
> URL: https://issues.apache.org/jira/browse/OOZIE-3240
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3240-002.patch, OOZIE-3240.txt
>
>
> The test TestJMSAccessorService#testConnectionRetry failed with the following 
> errors in the log:
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.oozie.service.TestJMSAccessorService.testConnectionRetry(TestJMSAccessorService.java:183)
> {noformat}
> {noformat}
> [jndiProperties=java.naming.factory.initial#org.apache.activemq.jndi.ActiveMQInitialContextFactory;java.naming.provider.url#tcp://localhost:39362;connectionFactoryNames#ConnectionFactory]]
> javax.jms.JMSException: Could not connect to broker URL: 
> tcp://localhost:39362. Reason: java.net.ConnectException: Connection refused 
> (Connection refused)
>   at 
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:36)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:373)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:303)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:243)
>   at 
> org.apache.oozie.jms.DefaultConnectionContext.createConnection(DefaultConnectionContext.java:53)
>   at 
> org.apache.oozie.service.JMSAccessorService.createConnectionContext(JMSAccessorService.java:264)
>   at 
> org.apache.oozie.service.JMSAccessorService.registerForNotification(JMSAccessorService.java:110)
>   at 
> org.apache.oozie.service.TestJMSAccessorService.testConnectionRetry(TestJMSAccessorService.java:173)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:255)
>   at junit.framework.TestSuite.run(TestSuite.java:250)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at 
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:410)
>   at 
> org.apache.maven.surefire.junitcore.pc.InvokerStrategy.schedule(InvokerStrategy.java:54)
>   at 
> org.apache.maven.surefire.junitcore.pc.Scheduler.schedule(Scheduler.java:367)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at 
> org.apache.maven.surefire.junitcore.pc.ParallelComputerBuilder$PC$1.run(ParallelComputerBuilder.java:593)
>   at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
>   at 
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
>   at 
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
>   at 
> org.apache.maven.surefire.juni

[jira] [Commented] (OOZIE-3246) Flaky test TestJMSJobEventListener#testConnectionDrop

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477200#comment-16477200
 ] 

Hadoop QA commented on OOZIE-3246:
--

PreCommit-OOZIE-Build started


> Flaky test TestJMSJobEventListener#testConnectionDrop
> -
>
> Key: OOZIE-3246
> URL: https://issues.apache.org/jira/browse/OOZIE-3246
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3246-001.patch
>
>
> The testcase TestJMSJobEventListener#testConnectionDrop occasionally fails 
> with the following error:
> {noformat}
> junit.framework.AssertionFailedError: 
> org.apache.activemq:type=Broker,brokerName=localhost
>   at 
> org.apache.oozie.jms.TestJMSJobEventListener.testConnectionDrop(TestJMSJobEventListener.java:365)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3250) Reduce heap waste by reducing duplicate byte[] count

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477198#comment-16477198
 ] 

Hadoop QA commented on OOZIE-3250:
--

PreCommit-OOZIE-Build started


> Reduce heap waste by reducing duplicate byte[] count
> 
>
> Key: OOZIE-3250
> URL: https://issues.apache.org/jira/browse/OOZIE-3250
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3250.001.patch, OOZIE-3250.002.patch, 
> OOZIE-3250.003.patch, OOZIE-3250.004.patch, OOZIE-3250.005.patch, 
> OOZIE-3250.006.patch
>
>
> Similar to OOZIE-3232, we also need to intern the {{byte[]}} field values 
> within 
> [*{{BinaryBlob}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/BinaryBlob.java#L32-L33]
>  and 
> [*{{StringBlob}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/StringBlob.java#L34]
>  to reduce heap waste caused by duplicate {{byte[]}} entries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3236) Flaky test TestHiveActionExecutor#testHiveAction

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477199#comment-16477199
 ] 

Hadoop QA commented on OOZIE-3236:
--

PreCommit-OOZIE-Build started


> Flaky test TestHiveActionExecutor#testHiveAction
> 
>
> Key: OOZIE-3236
> URL: https://issues.apache.org/jira/browse/OOZIE-3236
> Project: Oozie
>  Issue Type: Sub-task
>  Components: action, tests
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3236-001.patch, OOZIE-3236.txt
>
>
> The test TestHiveActionExecutor#testHiveAction failed with this error:
> {noformat}
> junit.framework.AssertionFailedError: YARN App state for app 
> application_1525471867439_0002 expected: but was:
>   at 
> org.apache.oozie.action.hadoop.TestHiveActionExecutor.testHiveAction(TestHiveActionExecutor.java:158)
> {noformat}
> https://builds.apache.org/job/PreCommit-OOZIE-Build/516/testReport/junit/org.apache.oozie.action.hadoop/TestHiveActionExecutor/testHiveAction/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3250) Reduce heap waste by reducing duplicate byte[] count

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477210#comment-16477210
 ] 

Peter Cseh commented on OOZIE-3250:
---

+1 (pending Jenkins on patch-6). The latest jhenkins run I could find is for 
patch-5.

> Reduce heap waste by reducing duplicate byte[] count
> 
>
> Key: OOZIE-3250
> URL: https://issues.apache.org/jira/browse/OOZIE-3250
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3250.001.patch, OOZIE-3250.002.patch, 
> OOZIE-3250.003.patch, OOZIE-3250.004.patch, OOZIE-3250.005.patch, 
> OOZIE-3250.006.patch
>
>
> Similar to OOZIE-3232, we also need to intern the {{byte[]}} field values 
> within 
> [*{{BinaryBlob}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/BinaryBlob.java#L32-L33]
>  and 
> [*{{StringBlob}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/StringBlob.java#L34]
>  to reduce heap waste caused by duplicate {{byte[]}} entries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (OOZIE-3250) Reduce heap waste by reducing duplicate byte[] count

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477210#comment-16477210
 ] 

Peter Cseh edited comment on OOZIE-3250 at 5/16/18 10:15 AM:
-

+1 (pending Jenkins on patch-6). The latest jhenkins run I could find is for 
patch-5.

edit: oh, it's started then


was (Author: gezapeti):
+1 (pending Jenkins on patch-6). The latest jhenkins run I could find is for 
patch-5.

> Reduce heap waste by reducing duplicate byte[] count
> 
>
> Key: OOZIE-3250
> URL: https://issues.apache.org/jira/browse/OOZIE-3250
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3250.001.patch, OOZIE-3250.002.patch, 
> OOZIE-3250.003.patch, OOZIE-3250.004.patch, OOZIE-3250.005.patch, 
> OOZIE-3250.006.patch
>
>
> Similar to OOZIE-3232, we also need to intern the {{byte[]}} field values 
> within 
> [*{{BinaryBlob}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/BinaryBlob.java#L32-L33]
>  and 
> [*{{StringBlob}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/StringBlob.java#L34]
>  to reduce heap waste caused by duplicate {{byte[]}} entries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-3228 PreCommit Build #538

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3228
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/538/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.75 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/distcp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2176 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3228

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run: 2132
Tests failed: 1
Tests errors: 1

The patch failed the following testcases:

testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)

Tests failing with errors:
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)

Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
TestOozieDBCLI#testOozieDBCLI
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)


The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/538/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  33340 0  100  3334  0   3896 --:--:-- --:--:-- --:--:--  
3894{"self":"https://issues.apache.org/jira/rest/api/2/issue/13154670/comment/16477232","id":"16477232","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall&ownerId=hadoopqa&avatarId=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium&ownerId=hadoopqa&avatarId=10393"},"displayName":"Hadoop
 QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting JIRA 
OOZIE-3228\n\nCleaning local git 
workspace\n\n\n\n{color:green}+1 
PATCH_APPLIES{color}\n{color:green}+1 CLEAN{color}\n{color:green}+1 

[jira] [Commented] (OOZIE-3226) Test case testOozieDBCLI() in oozie-tools fails with junit.framework.AssertionFailedError

[Peter Bacsko (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477230#comment-16477230
 ] 

Peter Bacsko commented on OOZIE-3226:
-

Yes, it started to fail after OOZIE-3192, although it's not directly caused by 
that change.

I can see two problems:
1. The method {{setUp()}} is marked with {{@BeforeClass}} but it does not have 
any effect, because JUnit3 test runner is selected for this class. The 
annotation is ignored.
2. Therefore {{setUp()}} runs again before {{testOozieDBCLI}} but this time the 
Derby database is not re-created. I'm not sure why, perhaps something is stored 
in a static field which prevents Derby from creating the database files again.

Anyway the root cause has been found and I'll upload the fix soon.

> Test case testOozieDBCLI() in oozie-tools fails with 
> junit.framework.AssertionFailedError
> -
>
> Key: OOZIE-3226
> URL: https://issues.apache.org/jira/browse/OOZIE-3226
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tools
> Environment: uname -a
> Linux pts00607-vm3 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:46 UTC 
> 2018 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Peter Bacsko
>Priority: Major
>
> Maven command used is : mvn -Dtest=TestOozieDBCLI test
> The test case testOozieDBCLI() in oozie-tools fails in the presence of the 
> test case testServicesDestroy()
> {code:java}
> [INFO] Running org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 33.539 s <<< FAILURE! - in org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] testOozieDBCLI(org.apache.oozie.tools.TestOozieDBCLI)  Time elapsed: 
> 4.289 s  <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
>     at 
> org.apache.oozie.tools.TestOozieDBCLI.testOozieDBCLI(TestOozieDBCLI.java:123)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]   TestOozieDBCLI.testOozieDBCLI:123 expected:<0> but was:<1>
> [INFO]
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3228) [Spark action] Can't load properties from spark-defaults.conf

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477232#comment-16477232
 ] 

Hadoop QA commented on OOZIE-3228:
--


Testing JIRA OOZIE-3228

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 2132
.Tests failed: 1
.Tests errors: 1

.The patch failed the following testcases:

testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)

.Tests failing with errors:
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)

.{color:orange}Tests failed at first run:{color}
TestJavaActionExecutor#testCredentialsSkip
TestOozieDBCLI#testOozieDBCLI
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

. https://builds.apache.org/job/PreCommit-OOZIE-Build/538/



> [Spark action] Can't load properties from spark-defaults.conf
> -
>
> Key: OOZIE-3228
> URL: https://issues.apache.org/jira/browse/OOZIE-3228
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Tang Yan
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3228.001.patch, OOZIE-3228.002.patch, 
> OOZIE-3228.003.patch, OOZIE-3228.004.patch
>
>
> When I create a Oozie workflow to launch a spark action, the spark job can't 
> load the configured properties in {{spark-defaults.conf}}. I've configured 
> each NodeManager as the Spark gateway role, so {{spark-defaults.conf}} is 
> generated in {{/etc/spark/conf/}} on each worker node.
> In {{spark-defaults.conf}} some configuration I've set into.
> {noformat}
> spark.executor.extraClassPath=/etc/hbase/conf:/etc/hive/conf
> spark.driver.extraClassPath=/etc/hbase/conf:/etc/hive/conf
> {noformat}
> But in the Oozie spark job, they're not loaded automatically.
> {noformat}
> --conf spark.executor.extraClassPath=$PWD/*
> --conf spark.driver.extraClassPath=$PWD/*
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3226) Test case testOozieDBCLI() in oozie-tools fails with junit.framework.AssertionFailedError

[Peter Bacsko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Bacsko updated OOZIE-3226:

Attachment: OOZIE-3226-001.patch

> Test case testOozieDBCLI() in oozie-tools fails with 
> junit.framework.AssertionFailedError
> -
>
> Key: OOZIE-3226
> URL: https://issues.apache.org/jira/browse/OOZIE-3226
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tools
> Environment: uname -a
> Linux pts00607-vm3 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:46 UTC 
> 2018 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3226-001.patch
>
>
> Maven command used is : mvn -Dtest=TestOozieDBCLI test
> The test case testOozieDBCLI() in oozie-tools fails in the presence of the 
> test case testServicesDestroy()
> {code:java}
> [INFO] Running org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 33.539 s <<< FAILURE! - in org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] testOozieDBCLI(org.apache.oozie.tools.TestOozieDBCLI)  Time elapsed: 
> 4.289 s  <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
>     at 
> org.apache.oozie.tools.TestOozieDBCLI.testOozieDBCLI(TestOozieDBCLI.java:123)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]   TestOozieDBCLI.testOozieDBCLI:123 expected:<0> but was:<1>
> [INFO]
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3226) Test case testOozieDBCLI() in oozie-tools fails with junit.framework.AssertionFailedError

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477248#comment-16477248
 ] 

Hadoop QA commented on OOZIE-3226:
--

PreCommit-OOZIE-Build started


> Test case testOozieDBCLI() in oozie-tools fails with 
> junit.framework.AssertionFailedError
> -
>
> Key: OOZIE-3226
> URL: https://issues.apache.org/jira/browse/OOZIE-3226
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tools
> Environment: uname -a
> Linux pts00607-vm3 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:46 UTC 
> 2018 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3226-001.patch
>
>
> Maven command used is : mvn -Dtest=TestOozieDBCLI test
> The test case testOozieDBCLI() in oozie-tools fails in the presence of the 
> test case testServicesDestroy()
> {code:java}
> [INFO] Running org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 33.539 s <<< FAILURE! - in org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] testOozieDBCLI(org.apache.oozie.tools.TestOozieDBCLI)  Time elapsed: 
> 4.289 s  <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
>     at 
> org.apache.oozie.tools.TestOozieDBCLI.testOozieDBCLI(TestOozieDBCLI.java:123)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]   TestOozieDBCLI.testOozieDBCLI:123 expected:<0> but was:<1>
> [INFO]
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Success: OOZIE-3240 PreCommit Build #542

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3240
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/542/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.75 MB...]
[DEBUG] There are no new bugs found in [sharelib/hcatalog].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/sqoop].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/oozie].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/streaming].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [webapp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [tools].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [docs].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2176 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3240

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [client].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 2131
Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
TestOozieDBCLI#testOozieDBCLI
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


+1 Overall result, good!, no -1s


The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/542/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/13157856/comment/16477260","id":"16477260","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/usera

[jira] [Commented] (OOZIE-3240) Flaky test TestJMSAccessorService#testConnectionRetry

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477260#comment-16477260
 ] 

Hadoop QA commented on OOZIE-3240:
--


Testing JIRA OOZIE-3240

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [client].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2131
.{color:orange}Tests failed at first run:{color}
TestJavaActionExecutor#testCredentialsSkip
TestOozieDBCLI#testOozieDBCLI
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{color}


The full output of the test-patch run is available at

. https://builds.apache.org/job/PreCommit-OOZIE-Build/542/



> Flaky test TestJMSAccessorService#testConnectionRetry
> -
>
> Key: OOZIE-3240
> URL: https://issues.apache.org/jira/browse/OOZIE-3240
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3240-002.patch, OOZIE-3240.txt
>
>
> The test TestJMSAccessorService#testConnectionRetry failed with the following 
> errors in the log:
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.oozie.service.TestJMSAccessorService.testConnectionRetry(TestJMSAccessorService.java:183)
> {noformat}
> {noformat}
> [jndiProperties=java.naming.factory.initial#org.apache.activemq.jndi.ActiveMQInitialContextFactory;java.naming.provider.url#tcp://localhost:39362;connectionFactoryNames#ConnectionFactory]]
> javax.jms.JMSException: Could not connect to broker URL: 
> tcp://localhost:39362. Reason: java.net.ConnectException: Connection refused 
> (Connection refused)
>   at 
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:36)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:373)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:303)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:243)
>   at 
> org.apache.oozie.jms.DefaultConnectionContext.createConnection(DefaultConnectionContext.java:53)
>   at 
> org.apache.oozie.service.JMSAccessorService.createConnectionContext(JMSAccessorService.java:264)
>   at 
> org.apache.oozie.service.

Failed: OOZIE-3246 PreCommit Build #541

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3246
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/541/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.79 MB...]
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [webapp].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run: 2131
Tests failed: 2
Tests errors: 27

The patch failed the following testcases:

testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerEhcache)
testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)

Tests failing with errors:
testDropEventTypeMessage(org.apache.oozie.jms.TestHCatMessageHandler)
testCacheUpdateByMessage(org.apache.oozie.jms.TestHCatMessageHandler)
testOnSLADurationMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAStartMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testSLAJobSelectorsNegative(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAEndMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAStartMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testSLAJobSelectors(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAEndMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLADurationMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)
testCoordinatorActionSelectors(org.apache.oozie.jms.TestJMSJobEventListener)
testCoordinatorActionSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectors(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobSuspendEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsAnd(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsOr(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorActionWaitingEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorActionStartEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobStartedEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testThreadLocalSession(org.apache.oozie.jms.TestDefaultConnectionContext)

Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
TestXCommand#testXCommandLifecycleLockingFailingToLock
TestCoordActionInputCheckXCommandNonUTC>TestCoordActionInputCheckXCommand#testNone
TestCoordActionsKillXCommand#testActionKillCommandDate
TestOozieDBCLI#testOozieDBCLI
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)


The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/541/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  55670 0  100  5567  0   7116 --:--:-- --:--:-- --:--:--  
7109{"self":"https://issues.apache.org/jira/rest/api/2/issue/13157874/comment/16477265","id":"16477265","author":{"self":"https://issues.apach

[jira] [Commented] (OOZIE-3246) Flaky test TestJMSJobEventListener#testConnectionDrop

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477265#comment-16477265
 ] 

Hadoop QA commented on OOZIE-3246:
--


Testing JIRA OOZIE-3246

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [webapp].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 2131
.Tests failed: 2
.Tests errors: 27

.The patch failed the following testcases:

testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerEhcache)
testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)

.Tests failing with errors:
testDropEventTypeMessage(org.apache.oozie.jms.TestHCatMessageHandler)
testCacheUpdateByMessage(org.apache.oozie.jms.TestHCatMessageHandler)
testOnSLADurationMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAStartMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testSLAJobSelectorsNegative(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAEndMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAStartMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testSLAJobSelectors(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAEndMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLADurationMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)
testCoordinatorActionSelectors(org.apache.oozie.jms.TestJMSJobEventListener)
testCoordinatorActionSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectors(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobSuspendEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsAnd(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsOr(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorActionWaitingEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorActionStartEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobStartedEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testThreadLocalSession(org.apache.oozie.jms.TestDefaultConnectionContext)

[jira] [Commented] (OOZIE-3246) Flaky test TestJMSJobEventListener#testConnectionDrop

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477267#comment-16477267
 ] 

Peter Cseh commented on OOZIE-3246:
---

The main fix here is this part:
{noformat}
+finally {
+if (broker != null) {
+broker.stop();
+}
{noformat}
right [~pbacsko]? 
E.g. A broker got stuck in some cases causing failures and we're making sure to 
stop it every case.
The other paces are just refactors if I see it correctly.

> Flaky test TestJMSJobEventListener#testConnectionDrop
> -
>
> Key: OOZIE-3246
> URL: https://issues.apache.org/jira/browse/OOZIE-3246
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3246-001.patch
>
>
> The testcase TestJMSJobEventListener#testConnectionDrop occasionally fails 
> with the following error:
> {noformat}
> junit.framework.AssertionFailedError: 
> org.apache.activemq:type=Broker,brokerName=localhost
>   at 
> org.apache.oozie.jms.TestJMSJobEventListener.testConnectionDrop(TestJMSJobEventListener.java:365)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3246) Flaky test TestJMSJobEventListener#testConnectionDrop

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477269#comment-16477269
 ] 

Peter Cseh commented on OOZIE-3246:
---

Oh, testConnectionDrop failed after the patch as well.
Do we need fixes from OOZIE-3240 as well?

> Flaky test TestJMSJobEventListener#testConnectionDrop
> -
>
> Key: OOZIE-3246
> URL: https://issues.apache.org/jira/browse/OOZIE-3246
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3246-001.patch
>
>
> The testcase TestJMSJobEventListener#testConnectionDrop occasionally fails 
> with the following error:
> {noformat}
> junit.framework.AssertionFailedError: 
> org.apache.activemq:type=Broker,brokerName=localhost
>   at 
> org.apache.oozie.jms.TestJMSJobEventListener.testConnectionDrop(TestJMSJobEventListener.java:365)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Success: OOZIE-3236 PreCommit Build #539

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3236
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/539/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.71 MB...]
[DEBUG] There are no new bugs found in [sharelib/oozie].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/pig].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [docs].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2176 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3236

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
+1 the patch adds/modifies 2 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [server].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 2131
Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
TestOozieDBCLI#testOozieDBCLI
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


+1 Overall result, good!, no -1s


The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/539/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/13157846/comment/16477272","id":"16477272","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall&ownerId=hadoopqa&avatarId=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium&ownerId=hadoopqa&avatarId=10393

[jira] [Commented] (OOZIE-3236) Flaky test TestHiveActionExecutor#testHiveAction

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477272#comment-16477272
 ] 

Hadoop QA commented on OOZIE-3236:
--


Testing JIRA OOZIE-3236

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [server].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2131
.{color:orange}Tests failed at first run:{color}
TestJavaActionExecutor#testCredentialsSkip
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
TestOozieDBCLI#testOozieDBCLI
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{color}


The full output of the test-patch run is available at

. https://builds.apache.org/job/PreCommit-OOZIE-Build/539/



> Flaky test TestHiveActionExecutor#testHiveAction
> 
>
> Key: OOZIE-3236
> URL: https://issues.apache.org/jira/browse/OOZIE-3236
> Project: Oozie
>  Issue Type: Sub-task
>  Components: action, tests
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3236-001.patch, OOZIE-3236.txt
>
>
> The test TestHiveActionExecutor#testHiveAction failed with this error:
> {noformat}
> junit.framework.AssertionFailedError: YARN App state for app 
> application_1525471867439_0002 expected: but was:
>   at 
> org.apache.oozie.action.hadoop.TestHiveActionExecutor.testHiveAction(TestHiveActionExecutor.java:158)
> {noformat}
> https://builds.apache.org/job/PreCommit-OOZIE-Build/516/testReport/junit/org.apache.oozie.action.hadoop/TestHiveActionExecutor/testHiveAction/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3246) Flaky test TestJMSJobEventListener#testConnectionDrop

[Peter Bacsko (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477274#comment-16477274
 ] 

Peter Bacsko commented on OOZIE-3246:
-

Yeah, this test run was disastrous. I think we have to apply all patches 
together to get rid of these. It's enough if we don't close the in-JVM broker 
once and it will affect all remaining tests which want to use JMS.

> Flaky test TestJMSJobEventListener#testConnectionDrop
> -
>
> Key: OOZIE-3246
> URL: https://issues.apache.org/jira/browse/OOZIE-3246
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3246-001.patch
>
>
> The testcase TestJMSJobEventListener#testConnectionDrop occasionally fails 
> with the following error:
> {noformat}
> junit.framework.AssertionFailedError: 
> org.apache.activemq:type=Broker,brokerName=localhost
>   at 
> org.apache.oozie.jms.TestJMSJobEventListener.testConnectionDrop(TestJMSJobEventListener.java:365)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3246) Flaky test TestJMSJobEventListener#testConnectionDrop

[Peter Bacsko (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477275#comment-16477275
 ] 

Peter Bacsko commented on OOZIE-3246:
-

bq. E.g. A broker got stuck in some cases causing failures and we're making 
sure to stop it every case.
bq. The other paces are just refactors if I see it correctly.

Yep, this is correct. {{BrokerService}} instances must be closed everywhere.

> Flaky test TestJMSJobEventListener#testConnectionDrop
> -
>
> Key: OOZIE-3246
> URL: https://issues.apache.org/jira/browse/OOZIE-3246
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3246-001.patch
>
>
> The testcase TestJMSJobEventListener#testConnectionDrop occasionally fails 
> with the following error:
> {noformat}
> junit.framework.AssertionFailedError: 
> org.apache.activemq:type=Broker,brokerName=localhost
>   at 
> org.apache.oozie.jms.TestJMSJobEventListener.testConnectionDrop(TestJMSJobEventListener.java:365)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-3250 PreCommit Build #540

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3250
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/540/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.71 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [docs].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2176 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build@2/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build@2/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3250

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [server].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run: 2132
Tests failed: 1
Tests errors: 0

The patch failed the following testcases:

testHiveAction(org.apache.oozie.action.hadoop.TestHiveActionExecutor)

Tests failing with errors:


Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
TestOozieDBCLI#testOozieDBCLI
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)


The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/540/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/13158435/comment/16477276","id":"16477276","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall&ownerId=hadoopqa&avatarId=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium&ownerId=hadoopqa&avatarId=10393"},"displayName":"Hadoop
 QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting JIRA 
OOZIE-3250\n\nCleaning local git 
workspace\n\n\n\n{color:green}+1 
PATCH_APPLIES{color}\n{color:green}+1 CLEAN{color}\n{color:green}+1 
RAW_PATCH_ANALYSIS{color}\n.{color:green}+1{color} the patch does not 
introduce any @author tags\n.{color:green}+1{color} the patch does not 
introduce any tabs\n.{color

[jira] [Commented] (OOZIE-3250) Reduce heap waste by reducing duplicate byte[] count

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477276#comment-16477276
 ] 

Hadoop QA commented on OOZIE-3250:
--


Testing JIRA OOZIE-3250

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [server].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 2132
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

testHiveAction(org.apache.oozie.action.hadoop.TestHiveActionExecutor)

.Tests failing with errors:


.{color:orange}Tests failed at first run:{color}
TestJavaActionExecutor#testCredentialsSkip
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
TestOozieDBCLI#testOozieDBCLI
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

. https://builds.apache.org/job/PreCommit-OOZIE-Build/540/



> Reduce heap waste by reducing duplicate byte[] count
> 
>
> Key: OOZIE-3250
> URL: https://issues.apache.org/jira/browse/OOZIE-3250
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3250.001.patch, OOZIE-3250.002.patch, 
> OOZIE-3250.003.patch, OOZIE-3250.004.patch, OOZIE-3250.005.patch, 
> OOZIE-3250.006.patch
>
>
> Similar to OOZIE-3232, we also need to intern the {{byte[]}} field values 
> within 
> [*{{BinaryBlob}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/BinaryBlob.java#L32-L33]
>  and 
> [*{{StringBlob}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/StringBlob.java#L34]
>  to reduce heap waste caused by duplicate {{byte[]}} entries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 67112: OOZIE-3228 [Spark action] Can't load properties from spark-defaults.conf

[András Piros via Review Board]

> On May 16, 2018, 9:57 a.m., Peter Cseh wrote:
> > sharelib/spark/src/main/java/org/apache/oozie/action/hadoop/SparkArgsExtractor.java
> > Lines 379-398 (patched)
> > 
> >
> > Can you also add this on the twiki level? Most users don't check the 
> > source code if something happens they don't expect.

Good idea! Added to `DG_SparkActionExtension.twiki`.


- András


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/67112/#review203207
---


On May 16, 2018, 9:23 a.m., András Piros wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67112/
> ---
> 
> (Updated May 16, 2018, 9:23 a.m.)
> 
> 
> Review request for oozie and Peter Cseh.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-3228 [Spark action] Can't load properties from spark-defaults.conf
> 
> 
> Diffs
> -
> 
>   
> sharelib/spark/src/main/java/org/apache/oozie/action/hadoop/SparkArgsExtractor.java
>  5af39cda52b403d8989fdd5d4f2524395a55580a 
>   
> sharelib/spark/src/test/java/org/apache/oozie/action/hadoop/TestSparkArgsExtractor.java
>  6a9baa5c7997198ab69f039f6a8884e49b13cad3 
> 
> 
> Diff: https://reviews.apache.org/r/67112/diff/3/
> 
> 
> Testing
> ---
> 
> `mvn clean test -Dtest=TestSparkArgsExtractor`
> 
> 
> Thanks,
> 
> András Piros
> 
>

[jira] [Commented] (OOZIE-3240) Flaky test TestJMSAccessorService#testConnectionRetry

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477277#comment-16477277
 ] 

Peter Cseh commented on OOZIE-3240:
---

The main fix here is  - similar to OOZIE-4246 - is to stop brokers in finally 
blocks, right? Seems legit.

You have removed the jmsService.destroy() call from the end. What is the reason 
for doing that? I'm not that familiar with JMS to know from the  top of my head.

> Flaky test TestJMSAccessorService#testConnectionRetry
> -
>
> Key: OOZIE-3240
> URL: https://issues.apache.org/jira/browse/OOZIE-3240
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3240-002.patch, OOZIE-3240.txt
>
>
> The test TestJMSAccessorService#testConnectionRetry failed with the following 
> errors in the log:
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.oozie.service.TestJMSAccessorService.testConnectionRetry(TestJMSAccessorService.java:183)
> {noformat}
> {noformat}
> [jndiProperties=java.naming.factory.initial#org.apache.activemq.jndi.ActiveMQInitialContextFactory;java.naming.provider.url#tcp://localhost:39362;connectionFactoryNames#ConnectionFactory]]
> javax.jms.JMSException: Could not connect to broker URL: 
> tcp://localhost:39362. Reason: java.net.ConnectException: Connection refused 
> (Connection refused)
>   at 
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:36)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:373)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:303)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:243)
>   at 
> org.apache.oozie.jms.DefaultConnectionContext.createConnection(DefaultConnectionContext.java:53)
>   at 
> org.apache.oozie.service.JMSAccessorService.createConnectionContext(JMSAccessorService.java:264)
>   at 
> org.apache.oozie.service.JMSAccessorService.registerForNotification(JMSAccessorService.java:110)
>   at 
> org.apache.oozie.service.TestJMSAccessorService.testConnectionRetry(TestJMSAccessorService.java:173)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:255)
>   at junit.framework.TestSuite.run(TestSuite.java:250)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at 
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:410)
>   at 
> org.apache.maven.surefire.junitcore.pc.InvokerStrategy.schedule(InvokerStrategy.java:54)
>   at 
> org.apache.maven.surefire.junitcore.pc.Scheduler.schedule(Scheduler.java:367)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at 
> org.apache.maven.surefire.junitcore.pc.ParallelComputerBuilder$PC$1.run(ParallelComputerBuilder.java:593)
>   at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
>   at 
> org.apache

[jira] [Updated] (OOZIE-3228) [Spark action] Can't load properties from spark-defaults.conf

[Andras Piros (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Piros updated OOZIE-3228:

Attachment: OOZIE-3228.005.patch

> [Spark action] Can't load properties from spark-defaults.conf
> -
>
> Key: OOZIE-3228
> URL: https://issues.apache.org/jira/browse/OOZIE-3228
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Tang Yan
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3228.001.patch, OOZIE-3228.002.patch, 
> OOZIE-3228.003.patch, OOZIE-3228.004.patch, OOZIE-3228.005.patch
>
>
> When I create a Oozie workflow to launch a spark action, the spark job can't 
> load the configured properties in {{spark-defaults.conf}}. I've configured 
> each NodeManager as the Spark gateway role, so {{spark-defaults.conf}} is 
> generated in {{/etc/spark/conf/}} on each worker node.
> In {{spark-defaults.conf}} some configuration I've set into.
> {noformat}
> spark.executor.extraClassPath=/etc/hbase/conf:/etc/hive/conf
> spark.driver.extraClassPath=/etc/hbase/conf:/etc/hive/conf
> {noformat}
> But in the Oozie spark job, they're not loaded automatically.
> {noformat}
> --conf spark.executor.extraClassPath=$PWD/*
> --conf spark.driver.extraClassPath=$PWD/*
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 67112: OOZIE-3228 [Spark action] Can't load properties from spark-defaults.conf

[András Piros via Review Board]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/67112/
---

(Updated May 16, 2018, 11:43 a.m.)


Review request for oozie and Peter Cseh.


Repository: oozie-git


Description
---

OOZIE-3228 [Spark action] Can't load properties from spark-defaults.conf


Diffs (updated)
-

  docs/src/site/twiki/DG_SparkActionExtension.twiki 
66076ff9d3098aeb06301458b900da8d7f5fb5db 
  
sharelib/spark/src/main/java/org/apache/oozie/action/hadoop/SparkArgsExtractor.java
 5af39cda52b403d8989fdd5d4f2524395a55580a 
  
sharelib/spark/src/test/java/org/apache/oozie/action/hadoop/TestSparkArgsExtractor.java
 6a9baa5c7997198ab69f039f6a8884e49b13cad3 


Diff: https://reviews.apache.org/r/67112/diff/4/

Changes: https://reviews.apache.org/r/67112/diff/3-4/


Testing
---

`mvn clean test -Dtest=TestSparkArgsExtractor`


Thanks,

András Piros

[jira] [Commented] (OOZIE-3236) Flaky test TestHiveActionExecutor#testHiveAction

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477278#comment-16477278
 ] 

Peter Cseh commented on OOZIE-3236:
---

It's worth a try to fix the test this way. +1


> Flaky test TestHiveActionExecutor#testHiveAction
> 
>
> Key: OOZIE-3236
> URL: https://issues.apache.org/jira/browse/OOZIE-3236
> Project: Oozie
>  Issue Type: Sub-task
>  Components: action, tests
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3236-001.patch, OOZIE-3236.txt
>
>
> The test TestHiveActionExecutor#testHiveAction failed with this error:
> {noformat}
> junit.framework.AssertionFailedError: YARN App state for app 
> application_1525471867439_0002 expected: but was:
>   at 
> org.apache.oozie.action.hadoop.TestHiveActionExecutor.testHiveAction(TestHiveActionExecutor.java:158)
> {noformat}
> https://builds.apache.org/job/PreCommit-OOZIE-Build/516/testReport/junit/org.apache.oozie.action.hadoop/TestHiveActionExecutor/testHiveAction/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3236) Fix flaky test TestHiveActionExecutor#testHiveAction

[Peter Cseh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Cseh updated OOZIE-3236:
--
Summary: Fix flaky test TestHiveActionExecutor#testHiveAction  (was: Flaky 
test TestHiveActionExecutor#testHiveAction)

> Fix flaky test TestHiveActionExecutor#testHiveAction
> 
>
> Key: OOZIE-3236
> URL: https://issues.apache.org/jira/browse/OOZIE-3236
> Project: Oozie
>  Issue Type: Sub-task
>  Components: action, tests
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3236-001.patch, OOZIE-3236.txt
>
>
> The test TestHiveActionExecutor#testHiveAction failed with this error:
> {noformat}
> junit.framework.AssertionFailedError: YARN App state for app 
> application_1525471867439_0002 expected: but was:
>   at 
> org.apache.oozie.action.hadoop.TestHiveActionExecutor.testHiveAction(TestHiveActionExecutor.java:158)
> {noformat}
> https://builds.apache.org/job/PreCommit-OOZIE-Build/516/testReport/junit/org.apache.oozie.action.hadoop/TestHiveActionExecutor/testHiveAction/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3228) [Spark action] Can't load properties from spark-defaults.conf

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477288#comment-16477288
 ] 

Hadoop QA commented on OOZIE-3228:
--

PreCommit-OOZIE-Build started


> [Spark action] Can't load properties from spark-defaults.conf
> -
>
> Key: OOZIE-3228
> URL: https://issues.apache.org/jira/browse/OOZIE-3228
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Tang Yan
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3228.001.patch, OOZIE-3228.002.patch, 
> OOZIE-3228.003.patch, OOZIE-3228.004.patch, OOZIE-3228.005.patch
>
>
> When I create a Oozie workflow to launch a spark action, the spark job can't 
> load the configured properties in {{spark-defaults.conf}}. I've configured 
> each NodeManager as the Spark gateway role, so {{spark-defaults.conf}} is 
> generated in {{/etc/spark/conf/}} on each worker node.
> In {{spark-defaults.conf}} some configuration I've set into.
> {noformat}
> spark.executor.extraClassPath=/etc/hbase/conf:/etc/hive/conf
> spark.driver.extraClassPath=/etc/hbase/conf:/etc/hive/conf
> {noformat}
> But in the Oozie spark job, they're not loaded automatically.
> {noformat}
> --conf spark.executor.extraClassPath=$PWD/*
> --conf spark.driver.extraClassPath=$PWD/*
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3246) Flaky test TestJMSJobEventListener#testConnectionDrop

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477285#comment-16477285
 ] 

Peter Cseh commented on OOZIE-3246:
---

OK then. I'm giving a +1 for this and for OOZIE-3240 as well so we can see if 
the issue goes away.

> Flaky test TestJMSJobEventListener#testConnectionDrop
> -
>
> Key: OOZIE-3246
> URL: https://issues.apache.org/jira/browse/OOZIE-3246
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3246-001.patch
>
>
> The testcase TestJMSJobEventListener#testConnectionDrop occasionally fails 
> with the following error:
> {noformat}
> junit.framework.AssertionFailedError: 
> org.apache.activemq:type=Broker,brokerName=localhost
>   at 
> org.apache.oozie.jms.TestJMSJobEventListener.testConnectionDrop(TestJMSJobEventListener.java:365)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3240) Flaky test TestJMSAccessorService#testConnectionRetry

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477287#comment-16477287
 ] 

Peter Cseh commented on OOZIE-3240:
---

+1 based on the discussion on OOZIE-3246

> Flaky test TestJMSAccessorService#testConnectionRetry
> -
>
> Key: OOZIE-3240
> URL: https://issues.apache.org/jira/browse/OOZIE-3240
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3240-002.patch, OOZIE-3240.txt
>
>
> The test TestJMSAccessorService#testConnectionRetry failed with the following 
> errors in the log:
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.oozie.service.TestJMSAccessorService.testConnectionRetry(TestJMSAccessorService.java:183)
> {noformat}
> {noformat}
> [jndiProperties=java.naming.factory.initial#org.apache.activemq.jndi.ActiveMQInitialContextFactory;java.naming.provider.url#tcp://localhost:39362;connectionFactoryNames#ConnectionFactory]]
> javax.jms.JMSException: Could not connect to broker URL: 
> tcp://localhost:39362. Reason: java.net.ConnectException: Connection refused 
> (Connection refused)
>   at 
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:36)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:373)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:303)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:243)
>   at 
> org.apache.oozie.jms.DefaultConnectionContext.createConnection(DefaultConnectionContext.java:53)
>   at 
> org.apache.oozie.service.JMSAccessorService.createConnectionContext(JMSAccessorService.java:264)
>   at 
> org.apache.oozie.service.JMSAccessorService.registerForNotification(JMSAccessorService.java:110)
>   at 
> org.apache.oozie.service.TestJMSAccessorService.testConnectionRetry(TestJMSAccessorService.java:173)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:255)
>   at junit.framework.TestSuite.run(TestSuite.java:250)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at 
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:410)
>   at 
> org.apache.maven.surefire.junitcore.pc.InvokerStrategy.schedule(InvokerStrategy.java:54)
>   at 
> org.apache.maven.surefire.junitcore.pc.Scheduler.schedule(Scheduler.java:367)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at 
> org.apache.maven.surefire.junitcore.pc.ParallelComputerBuilder$PC$1.run(ParallelComputerBuilder.java:593)
>   at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
>   at 
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
>   at 
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
>   at 
> org.apache.maven.s

[jira] [Commented] (OOZIE-3250) Reduce heap waste by reducing duplicate byte[] count

[Andras Piros (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477296#comment-16477296
 ] 

Andras Piros commented on OOZIE-3250:
-

Thanks [~gezapeti]! Failing tests are unrelated.

Committed to {{master}}.

> Reduce heap waste by reducing duplicate byte[] count
> 
>
> Key: OOZIE-3250
> URL: https://issues.apache.org/jira/browse/OOZIE-3250
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3250.001.patch, OOZIE-3250.002.patch, 
> OOZIE-3250.003.patch, OOZIE-3250.004.patch, OOZIE-3250.005.patch, 
> OOZIE-3250.006.patch
>
>
> Similar to OOZIE-3232, we also need to intern the {{byte[]}} field values 
> within 
> [*{{BinaryBlob}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/BinaryBlob.java#L32-L33]
>  and 
> [*{{StringBlob}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/StringBlob.java#L34]
>  to reduce heap waste caused by duplicate {{byte[]}} entries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3226) Test case testOozieDBCLI() in oozie-tools fails with junit.framework.AssertionFailedError

[Peter Bacsko (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477314#comment-16477314
 ] 

Peter Bacsko commented on OOZIE-3226:
-

[~andras.piros] [~gezapeti] please verify the proposed change.

> Test case testOozieDBCLI() in oozie-tools fails with 
> junit.framework.AssertionFailedError
> -
>
> Key: OOZIE-3226
> URL: https://issues.apache.org/jira/browse/OOZIE-3226
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tools
> Environment: uname -a
> Linux pts00607-vm3 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:46 UTC 
> 2018 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3226-001.patch
>
>
> Maven command used is : mvn -Dtest=TestOozieDBCLI test
> The test case testOozieDBCLI() in oozie-tools fails in the presence of the 
> test case testServicesDestroy()
> {code:java}
> [INFO] Running org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 33.539 s <<< FAILURE! - in org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] testOozieDBCLI(org.apache.oozie.tools.TestOozieDBCLI)  Time elapsed: 
> 4.289 s  <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
>     at 
> org.apache.oozie.tools.TestOozieDBCLI.testOozieDBCLI(TestOozieDBCLI.java:123)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]   TestOozieDBCLI.testOozieDBCLI:123 expected:<0> but was:<1>
> [INFO]
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3226) Test case testOozieDBCLI() in oozie-tools fails with junit.framework.AssertionFailedError

[Peter Bacsko (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477316#comment-16477316
 ] 

Peter Bacsko commented on OOZIE-3226:
-

Minor fix: {{dataBaseCreated}} should be spelled as {{databaseCreated}} 
(lower-case "b").

> Test case testOozieDBCLI() in oozie-tools fails with 
> junit.framework.AssertionFailedError
> -
>
> Key: OOZIE-3226
> URL: https://issues.apache.org/jira/browse/OOZIE-3226
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tools
> Environment: uname -a
> Linux pts00607-vm3 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:46 UTC 
> 2018 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3226-001.patch
>
>
> Maven command used is : mvn -Dtest=TestOozieDBCLI test
> The test case testOozieDBCLI() in oozie-tools fails in the presence of the 
> test case testServicesDestroy()
> {code:java}
> [INFO] Running org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 33.539 s <<< FAILURE! - in org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] testOozieDBCLI(org.apache.oozie.tools.TestOozieDBCLI)  Time elapsed: 
> 4.289 s  <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
>     at 
> org.apache.oozie.tools.TestOozieDBCLI.testOozieDBCLI(TestOozieDBCLI.java:123)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]   TestOozieDBCLI.testOozieDBCLI:123 expected:<0> but was:<1>
> [INFO]
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3226) Test case testOozieDBCLI() in oozie-tools fails with junit.framework.AssertionFailedError

[Andras Piros (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477323#comment-16477323
 ] 

Andras Piros commented on OOZIE-3226:
-

Thanks for the patch [~pbacsko]! I like the direction of the change, the root 
cause might be caused indeed by some {{static}} initializer block e.g. in 
{{derby}} code.

Nit: please employ {{\@Override}} annotation and {{super}} calls in {{setUp()}} 
and {{tearDown}}.

> Test case testOozieDBCLI() in oozie-tools fails with 
> junit.framework.AssertionFailedError
> -
>
> Key: OOZIE-3226
> URL: https://issues.apache.org/jira/browse/OOZIE-3226
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tools
> Environment: uname -a
> Linux pts00607-vm3 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:46 UTC 
> 2018 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3226-001.patch
>
>
> Maven command used is : mvn -Dtest=TestOozieDBCLI test
> The test case testOozieDBCLI() in oozie-tools fails in the presence of the 
> test case testServicesDestroy()
> {code:java}
> [INFO] Running org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 33.539 s <<< FAILURE! - in org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] testOozieDBCLI(org.apache.oozie.tools.TestOozieDBCLI)  Time elapsed: 
> 4.289 s  <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
>     at 
> org.apache.oozie.tools.TestOozieDBCLI.testOozieDBCLI(TestOozieDBCLI.java:123)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]   TestOozieDBCLI.testOozieDBCLI:123 expected:<0> but was:<1>
> [INFO]
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (OOZIE-3242) Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock

[Peter Bacsko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Bacsko reassigned OOZIE-3242:
---

Assignee: Peter Bacsko

> Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock
> -
>
> Key: OOZIE-3242
> URL: https://issues.apache.org/jira/browse/OOZIE-3242
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
>
> The test case TestXCommand#testXCommandLifecycleLockingFailingToLock 
> occasionally fails with the following error:
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.oozie.command.TestXCommand.testXCommandLifecycleLockingFailingToLock(TestXCommand.java:186)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3226) Test case testOozieDBCLI() in oozie-tools fails with junit.framework.AssertionFailedError

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477326#comment-16477326
 ] 

Peter Cseh commented on OOZIE-3226:
---

The change seems reasonable. I'll wait for Jenkins to see if the test case 
itself is fixed. 
I don't see a nice way to do @BeforeClass in Junit3 executor so we have to live 
with this workaround until the XTestCase is rewritten to Junit4

> Test case testOozieDBCLI() in oozie-tools fails with 
> junit.framework.AssertionFailedError
> -
>
> Key: OOZIE-3226
> URL: https://issues.apache.org/jira/browse/OOZIE-3226
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tools
> Environment: uname -a
> Linux pts00607-vm3 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:46 UTC 
> 2018 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3226-001.patch
>
>
> Maven command used is : mvn -Dtest=TestOozieDBCLI test
> The test case testOozieDBCLI() in oozie-tools fails in the presence of the 
> test case testServicesDestroy()
> {code:java}
> [INFO] Running org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 33.539 s <<< FAILURE! - in org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] testOozieDBCLI(org.apache.oozie.tools.TestOozieDBCLI)  Time elapsed: 
> 4.289 s  <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
>     at 
> org.apache.oozie.tools.TestOozieDBCLI.testOozieDBCLI(TestOozieDBCLI.java:123)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]   TestOozieDBCLI.testOozieDBCLI:123 expected:<0> but was:<1>
> [INFO]
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (OOZIE-3226) Test case testOozieDBCLI() in oozie-tools fails with junit.framework.AssertionFailedError

[Andras Piros (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477323#comment-16477323
 ] 

Andras Piros edited comment on OOZIE-3226 at 5/16/18 12:30 PM:
---

Thanks for the patch [~pbacsko]! I like the direction of the change, the root 
cause might be caused indeed by some {{static}} initializer block e.g. in 
{{derby}} code.

Nit: please employ {{\@Override}} annotation and {{super}} calls in {{setUp()}} 
and {{tearDown()}}.


was (Author: andras.piros):
Thanks for the patch [~pbacsko]! I like the direction of the change, the root 
cause might be caused indeed by some {{static}} initializer block e.g. in 
{{derby}} code.

Nit: please employ {{\@Override}} annotation and {{super}} calls in {{setUp()}} 
and {{tearDown}}.

> Test case testOozieDBCLI() in oozie-tools fails with 
> junit.framework.AssertionFailedError
> -
>
> Key: OOZIE-3226
> URL: https://issues.apache.org/jira/browse/OOZIE-3226
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tools
> Environment: uname -a
> Linux pts00607-vm3 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:46 UTC 
> 2018 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3226-001.patch
>
>
> Maven command used is : mvn -Dtest=TestOozieDBCLI test
> The test case testOozieDBCLI() in oozie-tools fails in the presence of the 
> test case testServicesDestroy()
> {code:java}
> [INFO] Running org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 33.539 s <<< FAILURE! - in org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] testOozieDBCLI(org.apache.oozie.tools.TestOozieDBCLI)  Time elapsed: 
> 4.289 s  <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
>     at 
> org.apache.oozie.tools.TestOozieDBCLI.testOozieDBCLI(TestOozieDBCLI.java:123)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]   TestOozieDBCLI.testOozieDBCLI:123 expected:<0> but was:<1>
> [INFO]
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3226) Test case testOozieDBCLI() in oozie-tools fails with junit.framework.AssertionFailedError

[Peter Bacsko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Bacsko updated OOZIE-3226:

Attachment: OOZIE-3226-002.patch

> Test case testOozieDBCLI() in oozie-tools fails with 
> junit.framework.AssertionFailedError
> -
>
> Key: OOZIE-3226
> URL: https://issues.apache.org/jira/browse/OOZIE-3226
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tools
> Environment: uname -a
> Linux pts00607-vm3 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:46 UTC 
> 2018 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3226-001.patch, OOZIE-3226-002.patch
>
>
> Maven command used is : mvn -Dtest=TestOozieDBCLI test
> The test case testOozieDBCLI() in oozie-tools fails in the presence of the 
> test case testServicesDestroy()
> {code:java}
> [INFO] Running org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 33.539 s <<< FAILURE! - in org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] testOozieDBCLI(org.apache.oozie.tools.TestOozieDBCLI)  Time elapsed: 
> 4.289 s  <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
>     at 
> org.apache.oozie.tools.TestOozieDBCLI.testOozieDBCLI(TestOozieDBCLI.java:123)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]   TestOozieDBCLI.testOozieDBCLI:123 expected:<0> but was:<1>
> [INFO]
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-3226 PreCommit Build #543

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3226
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/543/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.71 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/distcp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2176 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3226

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run: 2131
Tests failed: 1
Tests errors: 1

The patch failed the following testcases:

testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)

Tests failing with errors:
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)

Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)


The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/543/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/13154010/comment/16477372","id":"16477372","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall&ownerId=hadoopqa&avatarId=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium&ownerId=hadoopqa&avatarId=10393"},"displayName":"Hadoop
 QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting JIRA 
OOZIE-3226\n\nCleaning local git 
workspace\n\n\n\n{color:green}+1 
PATCH_APPLIES{color}\n{color:green}+1 CLEAN{color}\n{color:green}+1 
RAW_PATCH_ANALYSIS{color}\n. 

[jira] [Commented] (OOZIE-3226) Test case testOozieDBCLI() in oozie-tools fails with junit.framework.AssertionFailedError

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477372#comment-16477372
 ] 

Hadoop QA commented on OOZIE-3226:
--


Testing JIRA OOZIE-3226

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 2131
.Tests failed: 1
.Tests errors: 1

.The patch failed the following testcases:

testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)

.Tests failing with errors:
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)

.{color:orange}Tests failed at first run:{color}
TestJavaActionExecutor#testCredentialsSkip
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

. https://builds.apache.org/job/PreCommit-OOZIE-Build/543/



> Test case testOozieDBCLI() in oozie-tools fails with 
> junit.framework.AssertionFailedError
> -
>
> Key: OOZIE-3226
> URL: https://issues.apache.org/jira/browse/OOZIE-3226
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tools
> Environment: uname -a
> Linux pts00607-vm3 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:46 UTC 
> 2018 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3226-001.patch, OOZIE-3226-002.patch
>
>
> Maven command used is : mvn -Dtest=TestOozieDBCLI test
> The test case testOozieDBCLI() in oozie-tools fails in the presence of the 
> test case testServicesDestroy()
> {code:java}
> [INFO] Running org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 33.539 s <<< FAILURE! - in org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] testOozieDBCLI(org.apache.oozie.tools.TestOozieDBCLI)  Time elapsed: 
> 4.289 s  <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
>     at 
> org.apache.oozie.tools.TestOozieDBCLI.testOozieDBCLI(TestOozieDBCLI.java:123)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]   TestOozieDBCLI.testOozieDBCLI:123 expected:<0> but was:<1>
> [INFO]
> [ERROR] Tests run: 2, Failures: 1

[jira] [Commented] (OOZIE-3226) Test case testOozieDBCLI() in oozie-tools fails with junit.framework.AssertionFailedError

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477374#comment-16477374
 ] 

Hadoop QA commented on OOZIE-3226:
--

PreCommit-OOZIE-Build started


> Test case testOozieDBCLI() in oozie-tools fails with 
> junit.framework.AssertionFailedError
> -
>
> Key: OOZIE-3226
> URL: https://issues.apache.org/jira/browse/OOZIE-3226
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tools
> Environment: uname -a
> Linux pts00607-vm3 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:46 UTC 
> 2018 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3226-001.patch, OOZIE-3226-002.patch
>
>
> Maven command used is : mvn -Dtest=TestOozieDBCLI test
> The test case testOozieDBCLI() in oozie-tools fails in the presence of the 
> test case testServicesDestroy()
> {code:java}
> [INFO] Running org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 33.539 s <<< FAILURE! - in org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] testOozieDBCLI(org.apache.oozie.tools.TestOozieDBCLI)  Time elapsed: 
> 4.289 s  <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
>     at 
> org.apache.oozie.tools.TestOozieDBCLI.testOozieDBCLI(TestOozieDBCLI.java:123)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]   TestOozieDBCLI.testOozieDBCLI:123 expected:<0> but was:<1>
> [INFO]
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3242) Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock

[Peter Bacsko (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477375#comment-16477375
 ] 

Peter Bacsko commented on OOZIE-3242:
-

There's yet another fixed time sleep in this test. Patch is coming soon.

> Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock
> -
>
> Key: OOZIE-3242
> URL: https://issues.apache.org/jira/browse/OOZIE-3242
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
>
> The test case TestXCommand#testXCommandLifecycleLockingFailingToLock 
> occasionally fails with the following error:
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.oozie.command.TestXCommand.testXCommandLifecycleLockingFailingToLock(TestXCommand.java:186)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (OOZIE-3242) Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock

[Peter Bacsko (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477375#comment-16477375
 ] 

Peter Bacsko edited comment on OOZIE-3242 at 5/16/18 12:53 PM:
---

There's yet another fixed time sleep which causes a failure. Patch is coming 
soon.


was (Author: pbacsko):
There's yet another fixed time sleep in this test. Patch is coming soon.

> Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock
> -
>
> Key: OOZIE-3242
> URL: https://issues.apache.org/jira/browse/OOZIE-3242
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
>
> The test case TestXCommand#testXCommandLifecycleLockingFailingToLock 
> occasionally fails with the following error:
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.oozie.command.TestXCommand.testXCommandLifecycleLockingFailingToLock(TestXCommand.java:186)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3242) Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock

[Peter Bacsko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Bacsko updated OOZIE-3242:

Attachment: OOZIE-3242-001.patch

> Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock
> -
>
> Key: OOZIE-3242
> URL: https://issues.apache.org/jira/browse/OOZIE-3242
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3242-001.patch
>
>
> The test case TestXCommand#testXCommandLifecycleLockingFailingToLock 
> occasionally fails with the following error:
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.oozie.command.TestXCommand.testXCommandLifecycleLockingFailingToLock(TestXCommand.java:186)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3242) Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock

[Peter Bacsko (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477378#comment-16477378
 ] 

Peter Bacsko commented on OOZIE-3242:
-

[~gezapeti] / [~andras.piros] new patch to review.

> Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock
> -
>
> Key: OOZIE-3242
> URL: https://issues.apache.org/jira/browse/OOZIE-3242
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3242-001.patch
>
>
> The test case TestXCommand#testXCommandLifecycleLockingFailingToLock 
> occasionally fails with the following error:
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.oozie.command.TestXCommand.testXCommandLifecycleLockingFailingToLock(TestXCommand.java:186)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3226) Test case testOozieDBCLI() in oozie-tools fails with junit.framework.AssertionFailedError

[Andras Piros (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477384#comment-16477384
 ] 

Andras Piros commented on OOZIE-3226:
-

Thanks for the contribution [~pbacsko]! +1 (pending Jenkins for patch 002)

> Test case testOozieDBCLI() in oozie-tools fails with 
> junit.framework.AssertionFailedError
> -
>
> Key: OOZIE-3226
> URL: https://issues.apache.org/jira/browse/OOZIE-3226
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tools
> Environment: uname -a
> Linux pts00607-vm3 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:46 UTC 
> 2018 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3226-001.patch, OOZIE-3226-002.patch
>
>
> Maven command used is : mvn -Dtest=TestOozieDBCLI test
> The test case testOozieDBCLI() in oozie-tools fails in the presence of the 
> test case testServicesDestroy()
> {code:java}
> [INFO] Running org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 33.539 s <<< FAILURE! - in org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] testOozieDBCLI(org.apache.oozie.tools.TestOozieDBCLI)  Time elapsed: 
> 4.289 s  <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
>     at 
> org.apache.oozie.tools.TestOozieDBCLI.testOozieDBCLI(TestOozieDBCLI.java:123)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]   TestOozieDBCLI.testOozieDBCLI:123 expected:<0> but was:<1>
> [INFO]
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3242) Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477388#comment-16477388
 ] 

Hadoop QA commented on OOZIE-3242:
--

PreCommit-OOZIE-Build started


> Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock
> -
>
> Key: OOZIE-3242
> URL: https://issues.apache.org/jira/browse/OOZIE-3242
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3242-001.patch
>
>
> The test case TestXCommand#testXCommandLifecycleLockingFailingToLock 
> occasionally fails with the following error:
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.oozie.command.TestXCommand.testXCommandLifecycleLockingFailingToLock(TestXCommand.java:186)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3228) [Spark action] Can't load properties from spark-defaults.conf

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477403#comment-16477403
 ] 

Peter Cseh commented on OOZIE-3228:
---

+1 (pending jenkins) for patch 5

> [Spark action] Can't load properties from spark-defaults.conf
> -
>
> Key: OOZIE-3228
> URL: https://issues.apache.org/jira/browse/OOZIE-3228
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Tang Yan
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3228.001.patch, OOZIE-3228.002.patch, 
> OOZIE-3228.003.patch, OOZIE-3228.004.patch, OOZIE-3228.005.patch
>
>
> When I create a Oozie workflow to launch a spark action, the spark job can't 
> load the configured properties in {{spark-defaults.conf}}. I've configured 
> each NodeManager as the Spark gateway role, so {{spark-defaults.conf}} is 
> generated in {{/etc/spark/conf/}} on each worker node.
> In {{spark-defaults.conf}} some configuration I've set into.
> {noformat}
> spark.executor.extraClassPath=/etc/hbase/conf:/etc/hive/conf
> spark.driver.extraClassPath=/etc/hbase/conf:/etc/hive/conf
> {noformat}
> But in the Oozie spark job, they're not loaded automatically.
> {noformat}
> --conf spark.executor.extraClassPath=$PWD/*
> --conf spark.driver.extraClassPath=$PWD/*
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-3228 PreCommit Build #544

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3228
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/544/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.71 MB...]
[DEBUG] There are no new bugs found in [sharelib/distcp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2176 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build@2/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build@2/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3228

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run: 2132
Tests failed: 1
Tests errors: 1

The patch failed the following testcases:

testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)

Tests failing with errors:
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)

Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
TestOozieDBCLI#testOozieDBCLI
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)


The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/544/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/13154670/comment/16477415","id":"16477415","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall&ownerId=hadoopqa&avatarId=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium&ownerId=hadoopqa&avatarId=10393"},"displayName":"Hadoop
 QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting JIRA 
OOZIE-3228\n\nCleaning local git 
workspace\n\n\n\n{color:green}+1 
PATCH_APPLIES{color}\n{color:green}+1 CLEAN{color}\n{color:green}+1 
RAW_PATCH_ANALYSIS{color}\n.{color:green}+1{color} the patch does not 
introduce any @author tags\n.{color:green}+1{color} the patch does not 
intr

[jira] [Commented] (OOZIE-3228) [Spark action] Can't load properties from spark-defaults.conf

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477415#comment-16477415
 ] 

Hadoop QA commented on OOZIE-3228:
--


Testing JIRA OOZIE-3228

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 2132
.Tests failed: 1
.Tests errors: 1

.The patch failed the following testcases:

testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)

.Tests failing with errors:
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)

.{color:orange}Tests failed at first run:{color}
TestJavaActionExecutor#testCredentialsSkip
TestOozieDBCLI#testOozieDBCLI
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

. https://builds.apache.org/job/PreCommit-OOZIE-Build/544/



> [Spark action] Can't load properties from spark-defaults.conf
> -
>
> Key: OOZIE-3228
> URL: https://issues.apache.org/jira/browse/OOZIE-3228
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Tang Yan
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3228.001.patch, OOZIE-3228.002.patch, 
> OOZIE-3228.003.patch, OOZIE-3228.004.patch, OOZIE-3228.005.patch
>
>
> When I create a Oozie workflow to launch a spark action, the spark job can't 
> load the configured properties in {{spark-defaults.conf}}. I've configured 
> each NodeManager as the Spark gateway role, so {{spark-defaults.conf}} is 
> generated in {{/etc/spark/conf/}} on each worker node.
> In {{spark-defaults.conf}} some configuration I've set into.
> {noformat}
> spark.executor.extraClassPath=/etc/hbase/conf:/etc/hive/conf
> spark.driver.extraClassPath=/etc/hbase/conf:/etc/hive/conf
> {noformat}
> But in the Oozie spark job, they're not loaded automatically.
> {noformat}
> --conf spark.executor.extraClassPath=$PWD/*
> --conf spark.driver.extraClassPath=$PWD/*
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Web Console in Oozie 5

[Lars Francke]

Hi,

I've just tested Oozie 5 via CDH6 beta and I can't get the Web console
enabled using the "old" way there (dropping ext2.2 in /var/lib/oozie). Now
before I ping Cloudera itself I wanted to ask if anything has changed here
or if it _should_ work in Oozie 5?

I know you switched from Tomcat to Jetty so things might have changed. The
docs are still the same.

Cheers,
Lars

Re: Web Console in Oozie 5

[Andras Piros]

Hi Lars,

glad to hear you trying out Oozie 5 :)

As the *installation guide
*
tells:

> If a directory libext/ is present in Oozie installation directory, the
> oozie-setup.sh script will include all JARs in Jetty's webapp/WEB_INF/lib/
>  directory.
> If the ExtJS ZIP file is present in the libext/ directory, it will be
> added to the Jetty's webapp/ directory as well. The ExtJS library file
> name be ext-2.2.zip .


Important is to do that during setup, before calling oozie-setup.sh or
before the first call to oozied.sh.

Regards,

Andras

On Wed, May 16, 2018 at 3:19 PM, Lars Francke 
wrote:

> Hi,
>
> I've just tested Oozie 5 via CDH6 beta and I can't get the Web console
> enabled using the "old" way there (dropping ext2.2 in /var/lib/oozie). Now
> before I ping Cloudera itself I wanted to ask if anything has changed here
> or if it _should_ work in Oozie 5?
>
> I know you switched from Tomcat to Jetty so things might have changed. The
> docs are still the same.
>
> Cheers,
> Lars
>

Re: Web Console in Oozie 5

[Lars Francke]

Hi Andras,

thanks. All of that (used to be/is usually handled by Cloudera. But reading
between the lines it seems as if that should still work. In that case I'll
ping the Cloudera forum.

Cheers,
Lars

On Wed, May 16, 2018 at 4:02 PM, Andras Piros  wrote:

> Hi Lars,
>
> glad to hear you trying out Oozie 5 :)
>
> As the *installation guide
> *
> tells:
>
> > If a directory libext/ is present in Oozie installation directory, the
> > oozie-setup.sh script will include all JARs in Jetty's
> webapp/WEB_INF/lib/
> >  directory.
> > If the ExtJS ZIP file is present in the libext/ directory, it will be
> > added to the Jetty's webapp/ directory as well. The ExtJS library file
> > name be ext-2.2.zip .
>
>
> Important is to do that during setup, before calling oozie-setup.sh or
> before the first call to oozied.sh.
>
> Regards,
>
> Andras
>
> On Wed, May 16, 2018 at 3:19 PM, Lars Francke 
> wrote:
>
> > Hi,
> >
> > I've just tested Oozie 5 via CDH6 beta and I can't get the Web console
> > enabled using the "old" way there (dropping ext2.2 in /var/lib/oozie).
> Now
> > before I ping Cloudera itself I wanted to ask if anything has changed
> here
> > or if it _should_ work in Oozie 5?
> >
> > I know you switched from Tomcat to Jetty so things might have changed.
> The
> > docs are still the same.
> >
> > Cheers,
> > Lars
> >
>

Success: OOZIE-3226 PreCommit Build #545

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3226
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/545/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.71 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/streaming].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hcatalog].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/sqoop].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/oozie].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/distcp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2176 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3226

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 2132
Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
TestJMSAccessorService#testConnectionRetryExceptionListener
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


+1 Overall result, good!, no -1s


The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/545/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/13154010/comment/16477494","id":"16477494","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall&ownerId=hadoopqa&avatarId=10393","32x32":"https://iss

[jira] [Commented] (OOZIE-3226) Test case testOozieDBCLI() in oozie-tools fails with junit.framework.AssertionFailedError

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477494#comment-16477494
 ] 

Hadoop QA commented on OOZIE-3226:
--


Testing JIRA OOZIE-3226

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2132
.{color:orange}Tests failed at first run:{color}
TestJavaActionExecutor#testCredentialsSkip
TestJMSAccessorService#testConnectionRetryExceptionListener
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{color}


The full output of the test-patch run is available at

. https://builds.apache.org/job/PreCommit-OOZIE-Build/545/



> Test case testOozieDBCLI() in oozie-tools fails with 
> junit.framework.AssertionFailedError
> -
>
> Key: OOZIE-3226
> URL: https://issues.apache.org/jira/browse/OOZIE-3226
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tools
> Environment: uname -a
> Linux pts00607-vm3 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:46 UTC 
> 2018 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3226-001.patch, OOZIE-3226-002.patch
>
>
> Maven command used is : mvn -Dtest=TestOozieDBCLI test
> The test case testOozieDBCLI() in oozie-tools fails in the presence of the 
> test case testServicesDestroy()
> {code:java}
> [INFO] Running org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 33.539 s <<< FAILURE! - in org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] testOozieDBCLI(org.apache.oozie.tools.TestOozieDBCLI)  Time elapsed: 
> 4.289 s  <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
>     at 
> org.apache.oozie.tools.TestOozieDBCLI.testOozieDBCLI(TestOozieDBCLI.java:123)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]   TestOozieDBCLI.testOozieDBCLI:123 expected:<0> but was:<1>
> [INFO]
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3226) [tools] TestOozieDBCLI#testOozieDBCLI() fails

[Andras Piros (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Piros updated OOZIE-3226:

Summary: [tools] TestOozieDBCLI#testOozieDBCLI() fails  (was: Test case 
testOozieDBCLI() in oozie-tools fails with junit.framework.AssertionFailedError)

> [tools] TestOozieDBCLI#testOozieDBCLI() fails
> -
>
> Key: OOZIE-3226
> URL: https://issues.apache.org/jira/browse/OOZIE-3226
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tools
> Environment: uname -a
> Linux pts00607-vm3 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:46 UTC 
> 2018 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3226-001.patch, OOZIE-3226-002.patch
>
>
> Maven command used is : mvn -Dtest=TestOozieDBCLI test
> The test case testOozieDBCLI() in oozie-tools fails in the presence of the 
> test case testServicesDestroy()
> {code:java}
> [INFO] Running org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 33.539 s <<< FAILURE! - in org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] testOozieDBCLI(org.apache.oozie.tools.TestOozieDBCLI)  Time elapsed: 
> 4.289 s  <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
>     at 
> org.apache.oozie.tools.TestOozieDBCLI.testOozieDBCLI(TestOozieDBCLI.java:123)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]   TestOozieDBCLI.testOozieDBCLI:123 expected:<0> but was:<1>
> [INFO]
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Success: OOZIE-3242 PreCommit Build #546

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3242
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/546/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.71 MB...]
[DEBUG] There are no new bugs found in [sharelib/oozie].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/pig].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [docs].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2176 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3242

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [server].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 2132
Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
TestOozieDBCLI#testOozieDBCLI
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


+1 Overall result, good!, no -1s


The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/546/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/13157860/comment/16477515","id":"16477515","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall&ownerId=hadoopqa&avatarId=10393","32x32":"https://issue

[jira] [Commented] (OOZIE-3242) Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477515#comment-16477515
 ] 

Hadoop QA commented on OOZIE-3242:
--


Testing JIRA OOZIE-3242

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [server].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2132
.{color:orange}Tests failed at first run:{color}
TestJavaActionExecutor#testCredentialsSkip
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
TestOozieDBCLI#testOozieDBCLI
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{color}


The full output of the test-patch run is available at

. https://builds.apache.org/job/PreCommit-OOZIE-Build/546/



> Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock
> -
>
> Key: OOZIE-3242
> URL: https://issues.apache.org/jira/browse/OOZIE-3242
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3242-001.patch
>
>
> The test case TestXCommand#testXCommandLifecycleLockingFailingToLock 
> occasionally fails with the following error:
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.oozie.command.TestXCommand.testXCommandLifecycleLockingFailingToLock(TestXCommand.java:186)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (OOZIE-2968) TestJavaActionExecutor.testCredentialsSkip fails intermittently in Apache Oozie Core 5.0.0-SNAPSHOT

[Peter Bacsko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Bacsko reassigned OOZIE-2968:
---

Assignee: Peter Bacsko

> TestJavaActionExecutor.testCredentialsSkip fails intermittently in Apache 
> Oozie Core 5.0.0-SNAPSHOT
> ---
>
> Key: OOZIE-2968
> URL: https://issues.apache.org/jira/browse/OOZIE-2968
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tests
>Affects Versions: 5.0.0
> Environment: $ uname -a
> Linux pts00450-vm24 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 
> 17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Parita Johari
>Assignee: Peter Bacsko
>Priority: Minor
> Fix For: 5.1.0
>
>
> {code:java}
> Stacktrace
> org.apache.oozie.action.ActionExecutorException: JA020: Could not load 
> credentials of type [abc] with name [abcname]]; perhaps it was not defined in 
> oozie-site.xml?
>   at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.setCredentialTokens(JavaActionExecutor.java:1202)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor._testCredentialsSkip(TestJavaActionExecutor.java:1096)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor.testCredentialsSkip(TestJavaActionExecutor.java:995)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:255)
>   at junit.framework.TestSuite.run(TestSuite.java:250)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2968) TestJavaActionExecutor.testCredentialsSkip fails intermittently in Apache Oozie Core 5.0.0-SNAPSHOT

[Peter Bacsko (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477521#comment-16477521
 ] 

Peter Bacsko commented on OOZIE-2968:
-

I think I have this figured out. The outcome of this test depends on the 
ordering of the test case inside {{TestJavaActionExecutor}}. If a certain 
testcase runs earlier, then it fails, because the {{providerCache}} inside 
{{CredentialsProviderFactory}} is not refreshed. Therefore we have to call 
{{CredentialsProviderFactory.destroy()}} before this test.

> TestJavaActionExecutor.testCredentialsSkip fails intermittently in Apache 
> Oozie Core 5.0.0-SNAPSHOT
> ---
>
> Key: OOZIE-2968
> URL: https://issues.apache.org/jira/browse/OOZIE-2968
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tests
>Affects Versions: 5.0.0
> Environment: $ uname -a
> Linux pts00450-vm24 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 
> 17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Parita Johari
>Assignee: Peter Bacsko
>Priority: Minor
> Fix For: 5.1.0
>
>
> {code:java}
> Stacktrace
> org.apache.oozie.action.ActionExecutorException: JA020: Could not load 
> credentials of type [abc] with name [abcname]]; perhaps it was not defined in 
> oozie-site.xml?
>   at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.setCredentialTokens(JavaActionExecutor.java:1202)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor._testCredentialsSkip(TestJavaActionExecutor.java:1096)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor.testCredentialsSkip(TestJavaActionExecutor.java:995)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:255)
>   at junit.framework.TestSuite.run(TestSuite.java:250)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-2968) TestJavaActionExecutor.testCredentialsSkip fails intermittently in Apache Oozie Core 5.0.0-SNAPSHOT

[Peter Bacsko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Bacsko updated OOZIE-2968:

Attachment: OOZIE-2968-001.patch

> TestJavaActionExecutor.testCredentialsSkip fails intermittently in Apache 
> Oozie Core 5.0.0-SNAPSHOT
> ---
>
> Key: OOZIE-2968
> URL: https://issues.apache.org/jira/browse/OOZIE-2968
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tests
>Affects Versions: 5.0.0
> Environment: $ uname -a
> Linux pts00450-vm24 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 
> 17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Parita Johari
>Assignee: Peter Bacsko
>Priority: Minor
> Fix For: 5.1.0
>
> Attachments: OOZIE-2968-001.patch
>
>
> {code:java}
> Stacktrace
> org.apache.oozie.action.ActionExecutorException: JA020: Could not load 
> credentials of type [abc] with name [abcname]]; perhaps it was not defined in 
> oozie-site.xml?
>   at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.setCredentialTokens(JavaActionExecutor.java:1202)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor._testCredentialsSkip(TestJavaActionExecutor.java:1096)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor.testCredentialsSkip(TestJavaActionExecutor.java:995)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:255)
>   at junit.framework.TestSuite.run(TestSuite.java:250)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-2968) TestJavaActionExecutor.testCredentialsSkip fails intermittently in Apache Oozie Core 5.0.0-SNAPSHOT

[Peter Bacsko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Bacsko updated OOZIE-2968:

Priority: Major  (was: Minor)

> TestJavaActionExecutor.testCredentialsSkip fails intermittently in Apache 
> Oozie Core 5.0.0-SNAPSHOT
> ---
>
> Key: OOZIE-2968
> URL: https://issues.apache.org/jira/browse/OOZIE-2968
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tests
>Affects Versions: 5.0.0
> Environment: $ uname -a
> Linux pts00450-vm24 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 
> 17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Parita Johari
>Assignee: Peter Bacsko
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2968-001.patch
>
>
> {code:java}
> Stacktrace
> org.apache.oozie.action.ActionExecutorException: JA020: Could not load 
> credentials of type [abc] with name [abcname]]; perhaps it was not defined in 
> oozie-site.xml?
>   at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.setCredentialTokens(JavaActionExecutor.java:1202)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor._testCredentialsSkip(TestJavaActionExecutor.java:1096)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor.testCredentialsSkip(TestJavaActionExecutor.java:995)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:255)
>   at junit.framework.TestSuite.run(TestSuite.java:250)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2968) TestJavaActionExecutor.testCredentialsSkip fails intermittently in Apache Oozie Core 5.0.0-SNAPSHOT

[Peter Bacsko (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477542#comment-16477542
 ] 

Peter Bacsko commented on OOZIE-2968:
-

[~gezapeti] [~andras.piros] take a look please.

> TestJavaActionExecutor.testCredentialsSkip fails intermittently in Apache 
> Oozie Core 5.0.0-SNAPSHOT
> ---
>
> Key: OOZIE-2968
> URL: https://issues.apache.org/jira/browse/OOZIE-2968
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tests
>Affects Versions: 5.0.0
> Environment: $ uname -a
> Linux pts00450-vm24 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 
> 17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Parita Johari
>Assignee: Peter Bacsko
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2968-001.patch
>
>
> {code:java}
> Stacktrace
> org.apache.oozie.action.ActionExecutorException: JA020: Could not load 
> credentials of type [abc] with name [abcname]]; perhaps it was not defined in 
> oozie-site.xml?
>   at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.setCredentialTokens(JavaActionExecutor.java:1202)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor._testCredentialsSkip(TestJavaActionExecutor.java:1096)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor.testCredentialsSkip(TestJavaActionExecutor.java:995)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:255)
>   at junit.framework.TestSuite.run(TestSuite.java:250)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2968) TestJavaActionExecutor.testCredentialsSkip fails intermittently in Apache Oozie Core 5.0.0-SNAPSHOT

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477558#comment-16477558
 ] 

Hadoop QA commented on OOZIE-2968:
--

PreCommit-OOZIE-Build started


> TestJavaActionExecutor.testCredentialsSkip fails intermittently in Apache 
> Oozie Core 5.0.0-SNAPSHOT
> ---
>
> Key: OOZIE-2968
> URL: https://issues.apache.org/jira/browse/OOZIE-2968
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tests
>Affects Versions: 5.0.0
> Environment: $ uname -a
> Linux pts00450-vm24 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 
> 17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Parita Johari
>Assignee: Peter Bacsko
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2968-001.patch
>
>
> {code:java}
> Stacktrace
> org.apache.oozie.action.ActionExecutorException: JA020: Could not load 
> credentials of type [abc] with name [abcname]]; perhaps it was not defined in 
> oozie-site.xml?
>   at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.setCredentialTokens(JavaActionExecutor.java:1202)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor._testCredentialsSkip(TestJavaActionExecutor.java:1096)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor.testCredentialsSkip(TestJavaActionExecutor.java:995)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:255)
>   at junit.framework.TestSuite.run(TestSuite.java:250)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 66656: Exclusion pattern for sharelib.

[Mate Juhasz]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/66656/
---

(Updated May 16, 2018, 3:37 p.m.)


Review request for oozie, András Piros and Denes Bodo.


Changes
---

Created separate ShareLibExcluder class, filtering is done on the full path 
(excluding the sharelib root), modified tests according to behaviour change 
(these could be put into a separate class + JavaActionExecutor test rework may 
be needed). I tried to take into account your proposals, but I kindly ask you 
to review this new patch and waiting for your opinion about it. Thanks!


Bugs: OOZIE-1624
https://issues.apache.org/jira/browse/OOZIE-1624


Repository: oozie-git


Description
---

OOZIE-1624 Exclusion pattern for sharelib.


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
0ba3cbf9 
  core/src/main/java/org/apache/oozie/action/hadoop/ShareLibExcluder.java 
PRE-CREATION 
  core/src/main/java/org/apache/oozie/service/ShareLibService.java a901567d 
  core/src/test/java/org/apache/oozie/service/TestShareLibService.java d2441661 


Diff: https://reviews.apache.org/r/66656/diff/2/

Changes: https://reviews.apache.org/r/66656/diff/1-2/


Testing
---

Tested on a cluster


Thanks,

Mate Juhasz

Success: OOZIE-2968 PreCommit Build #547

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2968
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/547/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.74 MB...]
[DEBUG] There are no new bugs found in [sharelib/sqoop].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/distcp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/pig].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hcatalog].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [tools].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2176 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-2968

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [examples].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 2133
Tests failed at first run:
TestOozieDBCLI#testOozieDBCLI
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


+1 Overall result, good!, no -1s


The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/547/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  29680 0  100  2968  0   3506 --:--:-- --:--:-- --:--:--  
3504{"self":"https://issues.apache.org/jira/rest/api/2/issue/13082077/comment/16477735","id":"16477735","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall&ownerId=hadoopqa&av

[jira] [Commented] (OOZIE-2968) TestJavaActionExecutor.testCredentialsSkip fails intermittently in Apache Oozie Core 5.0.0-SNAPSHOT

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477735#comment-16477735
 ] 

Hadoop QA commented on OOZIE-2968:
--


Testing JIRA OOZIE-2968

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [examples].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2133
.{color:orange}Tests failed at first run:{color}
TestOozieDBCLI#testOozieDBCLI
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{color}


The full output of the test-patch run is available at

. https://builds.apache.org/job/PreCommit-OOZIE-Build/547/



> TestJavaActionExecutor.testCredentialsSkip fails intermittently in Apache 
> Oozie Core 5.0.0-SNAPSHOT
> ---
>
> Key: OOZIE-2968
> URL: https://issues.apache.org/jira/browse/OOZIE-2968
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tests
>Affects Versions: 5.0.0
> Environment: $ uname -a
> Linux pts00450-vm24 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 
> 17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Parita Johari
>Assignee: Peter Bacsko
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2968-001.patch
>
>
> {code:java}
> Stacktrace
> org.apache.oozie.action.ActionExecutorException: JA020: Could not load 
> credentials of type [abc] with name [abcname]]; perhaps it was not defined in 
> oozie-site.xml?
>   at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.setCredentialTokens(JavaActionExecutor.java:1202)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor._testCredentialsSkip(TestJavaActionExecutor.java:1096)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor.testCredentialsSkip(TestJavaActionExecutor.java:995)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:

[jira] [Commented] (OOZIE-2968) TestJavaActionExecutor.testCredentialsSkip fails intermittently in Apache Oozie Core 5.0.0-SNAPSHOT

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16478010#comment-16478010
 ] 

Peter Cseh commented on OOZIE-2968:
---

If Jenkins give a +1 who am I do object?
+1

> TestJavaActionExecutor.testCredentialsSkip fails intermittently in Apache 
> Oozie Core 5.0.0-SNAPSHOT
> ---
>
> Key: OOZIE-2968
> URL: https://issues.apache.org/jira/browse/OOZIE-2968
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tests
>Affects Versions: 5.0.0
> Environment: $ uname -a
> Linux pts00450-vm24 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 
> 17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Parita Johari
>Assignee: Peter Bacsko
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2968-001.patch
>
>
> {code:java}
> Stacktrace
> org.apache.oozie.action.ActionExecutorException: JA020: Could not load 
> credentials of type [abc] with name [abcname]]; perhaps it was not defined in 
> oozie-site.xml?
>   at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.setCredentialTokens(JavaActionExecutor.java:1202)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor._testCredentialsSkip(TestJavaActionExecutor.java:1096)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor.testCredentialsSkip(TestJavaActionExecutor.java:995)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:255)
>   at junit.framework.TestSuite.run(TestSuite.java:250)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-2968) TestJavaActionExecutor.testCredentialsSkip fails intermittently

[Peter Cseh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Cseh updated OOZIE-2968:
--
Summary: TestJavaActionExecutor.testCredentialsSkip fails intermittently  
(was: TestJavaActionExecutor.testCredentialsSkip fails intermittently in Apache 
Oozie Core 5.0.0-SNAPSHOT)

> TestJavaActionExecutor.testCredentialsSkip fails intermittently
> ---
>
> Key: OOZIE-2968
> URL: https://issues.apache.org/jira/browse/OOZIE-2968
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tests
>Affects Versions: 5.0.0
> Environment: $ uname -a
> Linux pts00450-vm24 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 
> 17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Parita Johari
>Assignee: Peter Bacsko
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2968-001.patch
>
>
> {code:java}
> Stacktrace
> org.apache.oozie.action.ActionExecutorException: JA020: Could not load 
> credentials of type [abc] with name [abcname]]; perhaps it was not defined in 
> oozie-site.xml?
>   at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.setCredentialTokens(JavaActionExecutor.java:1202)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor._testCredentialsSkip(TestJavaActionExecutor.java:1096)
>   at 
> org.apache.oozie.action.hadoop.TestJavaActionExecutor.testCredentialsSkip(TestJavaActionExecutor.java:995)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:255)
>   at junit.framework.TestSuite.run(TestSuite.java:250)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3242) Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16478076#comment-16478076
 ] 

Peter Cseh commented on OOZIE-3242:
---

Replacing sleeps with latches fixed many of the flakies before.
Maybe we should consider looking for the word "sleep" in the pre-commit and 
give a -1 for it :)
+1

> Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock
> -
>
> Key: OOZIE-3242
> URL: https://issues.apache.org/jira/browse/OOZIE-3242
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3242-001.patch
>
>
> The test case TestXCommand#testXCommandLifecycleLockingFailingToLock 
> occasionally fails with the following error:
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.oozie.command.TestXCommand.testXCommandLifecycleLockingFailingToLock(TestXCommand.java:186)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (103 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3249  [tools] Instrumentation log parser
https://issues.apache.org/jira/browse/OOZIE-3249
OOZIE-3221  Rename DEFAULT_LAUNCHER_MAX_ATTEMPS
https://issues.apache.org/jira/browse/OOZIE-3221
OOZIE-3218  Oozie Sqoop action with command splits the select clause into 
multiple parts due to delimiter being space
https://issues.apache.org/jira/browse/OOZIE-3218
OOZIE-3199  Let system property restriction configurable
https://issues.apache.org/jira/browse/OOZIE-3199
OOZIE-3196  Authorization: restrict world readability by user
https://issues.apache.org/jira/browse/OOZIE-3196
OOZIE-3194  Oozie should set proper permissions to sharelib after upload
https://issues.apache.org/jira/browse/OOZIE-3194
OOZIE-3193  Applications are not killed when submitted via subworkflow
https://issues.apache.org/jira/browse/OOZIE-3193
OOZIE-3186  Oozie is unable to use configuration linked using jceks://file/...
https://issues.apache.org/jira/browse/OOZIE-3186
OOZIE-3185  Conflicting JARs org.apache.derby exist in Oozie
https://issues.apache.org/jira/browse/OOZIE-3185
OOZIE-3179  Adding a configurable config-default.xml location to a workflow
https://issues.apache.org/jira/browse/OOZIE-3179
OOZIE-3170  Oozie Diagnostic Bundle tool fails with NPE due to missing service 
class
https://issues.apache.org/jira/browse/OOZIE-3170
OOZIE-3135  Configure log4j2 in SqoopMain
https://issues.apache.org/jira/browse/OOZIE-3135
OOZIE-3109  Escape log-streaming's HTML-specific characters
https://issues.apache.org/jira/browse/OOZIE-3109
OOZIE-3094  fix for grammar mistake
https://issues.apache.org/jira/browse/OOZIE-3094
OOZIE-3091  Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: 
org/apache/avro/mapred/AvroWrapper"
https://issues.apache.org/jira/browse/OOZIE-3091
OOZIE-3071  Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 
than Spark 2.2.0
https://issues.apache.org/jira/browse/OOZIE-3071
OOZIE-3063  Sanitizing variables that are part of openjpa.ConnectionProperties
https://issues.apache.org/jira/browse/OOZIE-3063
OOZIE-3062  Set HADOOP_CONF_DIR for spark action
https://issues.apache.org/jira/browse/OOZIE-3062
OOZIE-3061  Kill only those child jobs which are not already killed
https://issues.apache.org/jira/browse/OOZIE-3061
OOZIE-3002  address findbugs errors in client lib
https://issues.apache.org/jira/browse/OOZIE-3002
OOZIE-2975  code clean up in pig sharelib, replace Exception with more 
explicit, add try with resources, StringBuilder instead of StringBuffer
https://issues.apache.org/jira/browse/OOZIE-2975
OOZIE-2956  Fix Findbugs warnings related to reliance on default encoding in 
oozie-core
https://issues.apache.org/jira/browse/OOZIE-2956
OOZIE-2955  Fix Findbugs warnings related to reliance on default encoding in 
oozie-client
https://issues.apache.org/jira/browse/OOZIE-2955
OOZIE-2954  Fix Checkstyle issues in oozie-client
https://issues.apache.org/jira/browse/OOZIE-2954
OOZIE-2953  Fix Checkstyle issues in oozie-tools
https://issues.apache.org/jira/browse/OOZIE-2953
OOZIE-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues.apache.org/jira/browse/OOZIE-2952
OOZIE-2949  Escape quotes whitespaces in Sqoop  field
https://issues.apache.org/jira/browse/OOZIE-2949
OOZIE-2942  [examples] Fix Findbugs warnings
https://issues.apache.org/jira/browse/OOZIE-2942
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
OOZIE-2883  OOZIE throw the error "Missing 
[oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
 property"
https://issues.apache.org/jira/browse/OOZIE-2883
OOZIE-2877  Oozie Git Action
https://issues.apache.org/jira/browse/OOZIE-2877
OOZIE-2867  Timezone handling for Coordinators: emphasize "Continent/City" 
format
https://issues.apache.org/jira/browse/OOZIE-2867
OOZIE-2834  ParameterVerifier logging non-useful warning for workflow definition
https://issues.apache.org/jira/browse/OOZIE-2834
OOZIE-2833  when using uber mode the regex pattern used in the 
extractHeapSizeMB method does not allow heap sizes specified in bytes.
https://issues.apache.org/jira/browse/OOZIE-2833
OOZIE-2829  Improve sharelib upload to accept multiple source folders
https://issues.apache.org/jira/browse/OOZIE-2829
OOZIE-2826  Falcon feed fails to aws s3; Oozie joda time version does not meet 
required jar version 2.2 or later
https://issues.apache.org/jira/browse/OOZIE-2826
OOZIE-2