[jira] Subscription: Oozie Patch Available

2017-11-07 Thread jira
Issue Subscription
Filter: Oozie Patch Available (109 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3106  upgrade surefire-plugin to 2.20.1
https://issues.apache.org/jira/browse/OOZIE-3106
OOZIE-3105  testJMXInstrumentation from the 
org.apache.oozie.util.TestMetricsInstrumentation class is flaky
https://issues.apache.org/jira/browse/OOZIE-3105
OOZIE-3101  Oozie should add error message to the response body
https://issues.apache.org/jira/browse/OOZIE-3101
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-3083  Make improved version Info backward compatible
https://issues.apache.org/jira/browse/OOZIE-3083
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-3022  fix for warning has no file and won't be listed in dependency files 
details
https://issues.apache.org/jira/browse/OOZIE-3022
OOZIE-3002  address findbugs errors in client lib
https://issues.apache.org/jira/browse/OOZIE-3002
OOZIE-3001  core library has many instances of warnings with trailing spaces 
and lines longer than 132 chars
https://issues.apache.org/jira/browse/OOZIE-3001
OOZIE-2997  files contain trailing white spaces in client lib
https://issues.apache.org/jira/browse/OOZIE-2997
OOZIE-2996  add option for -UseGCOverheadLimit to maven opts as sometimes local 
testing fails
https://issues.apache.org/jira/browse/OOZIE-2996
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-2969  Drop support for Java 1.7
https://issues.apache.org/jira/browse/OOZIE-2969
OOZIE-2964  Add -Xdoclint:none to javadoc opts to avoid warnings
https://issues.apache.org/jira/browse/OOZIE-2964
OOZIE-2957  Documentation states that starting a coordinator is possible
https://issues.apache.org/jira/browse/OOZIE-2957
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  Fix Findbugs warnings in oozie-examples
https://issues.apache.org/jira/browse/OOZIE-2942
OOZIE-2937  Remove redundant groupId from the child pom's
https://issues.apache.org/jira/browse/OOZIE-2937
OOZIE-2934  Fix "Exceptional return value of java.io.File.mkdirs() ignored" 
Findbugs error in oozie-sharelib-spark
https://issues.apache.org/jira/browse/OOZIE-2934
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
OOZIE-2914  Consolidate Trim 
https://issues.apache.org/jira/browse/OOZIE-2914
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 la

[jira] [Commented] (OOZIE-3091) Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: org/apache/avro/mapred/AvroWrapper"

2017-11-07 Thread Prabhu Joseph (JIRA)

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

Prabhu Joseph commented on OOZIE-3091:
--

Hi [~dbist13], have you had a chance to look into this.

> Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: 
> org/apache/avro/mapred/AvroWrapper"
> ---
>
> Key: OOZIE-3091
> URL: https://issues.apache.org/jira/browse/OOZIE-3091
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.2.0
>Reporter: Prabhu Joseph
>Assignee: Prabhu Joseph
> Attachments: OOZIE-3091.1.patch, OOZIE-3091.2.patch, 
> Oozie_Sqoop_Avro_import
>
>
> Oozie Sqoop Action which does Import as avro fails with below. 
> avro-mapred-1.8.0-hadoop2.jar need to be included in Oozie Sqoop Sharelib
> {code}
> 2017-10-19 09:45:25,349 WARN [main] org.apache.hadoop.mapred.YarnChild: 
> Exception running child : java.lang.RuntimeException: 
> java.lang.reflect.InvocationTargetException
> at 
> org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:134)
> at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:745)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:170)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:164)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at 
> org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:132)
> ... 7 more
> Caused by: java.lang.NoClassDefFoundError: org/apache/avro/mapred/AvroWrapper
> at 
> org.apache.sqoop.mapreduce.AvroImportMapper.(AvroImportMapper.java:43)
> ... 12 more
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.avro.mapred.AvroWrapper
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 13 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Failed: OOZIE-3101 PreCommit Build #190

2017-11-07 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/OOZIE-3101
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/190/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.61 MB...]
+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 [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: 2055
Tests failed: 1
Tests errors: 0

The patch failed the following testcases:

  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

Tests failing with errors:
  

+1 DISTRO
+1 distro tarball builds with the patch 


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

 There is at least one warning, please check

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

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

  % 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
 14 3706k   14  541k0 0   785k  0  0:00:04 --:--:--  0:00:04  
785k100 3706k  100 3706k0 0  4943k  0 --:--:-- --:--:-- --:--:-- 
51.5M
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-3101
Archiving artifacts
[Fast Archiver] Compressed 1.81 MB of artifacts by 24.2% relative to #164
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  
org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup

Error Message:
expected: but was:

Stack Trace:
junit.framework.AssertionFailedError: expected: 
but was:
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:86)
at junit.framework.TestCase.assertEquals(TestCase.java:253)
at 
org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup(TestCoordMaterializeTransitionXCommand.java:582)
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:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.ru

[jira] [Commented] (OOZIE-3101) Oozie should add error message to the response body

2017-11-07 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-3101:
--

Testing JIRA OOZIE-3101

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 does adds/modifies 3 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:red}WARNING{color}: the current HEAD has 77 Javadoc warning(s)
{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 [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:red}-1 TESTS{color}
.Tests run: 2055
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

.Tests failing with errors:
.  

{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}

{color:red}. There is at least one warning, please check{color}

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

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

> Oozie should add error message to the response body
> ---
>
> Key: OOZIE-3101
> URL: https://issues.apache.org/jira/browse/OOZIE-3101
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-3101-1.patch, OOZIE-3101-2.patch, 
> OOZIE-3101-3.patch, OOZIE-3101-4.patch, OOZIE-3101-5.patch
>
>
> For web service APIs, currently Oozie adds error message in a custom response 
> header which is parsed out by the OozieClient. Oozie should also put error 
> message in the response body so that clients like curl can display the error 
> message to users without having to turn on verbose output



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (OOZIE-3111) [Umbrella] Fix flaky tests in Oozie

2017-11-07 Thread Peter Bacsko (JIRA)

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

Peter Bacsko updated OOZIE-3111:

Component/s: tests

> [Umbrella] Fix flaky tests in Oozie
> ---
>
> Key: OOZIE-3111
> URL: https://issues.apache.org/jira/browse/OOZIE-3111
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Reporter: Peter Bacsko
>
> In Oozie, we've had a number or flaky tests for quite a while. In order to 
> have successful builds, we circumvented the problem by re-running failed 
> tests. But this is not a good long-term solution.
> This JIRA tracks the tests that are currently flaky. We should address each 
> of these tests to have stable builds.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (OOZIE-3111) [Umbrella] Fix flaky tests in Oozie

2017-11-07 Thread Peter Bacsko (JIRA)

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

Peter Bacsko commented on OOZIE-3111:
-

Soon I'll create subtasks for each testcase.

> [Umbrella] Fix flaky tests in Oozie
> ---
>
> Key: OOZIE-3111
> URL: https://issues.apache.org/jira/browse/OOZIE-3111
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Reporter: Peter Bacsko
>
> In Oozie, we've had a number or flaky tests for quite a while. In order to 
> have successful builds, we circumvented the problem by re-running failed 
> tests. But this is not a good long-term solution.
> This JIRA tracks the tests that are currently flaky. We should address each 
> of these tests to have stable builds.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (OOZIE-3111) [Umbrella] Fix flaky tests in Oozie

2017-11-07 Thread Peter Bacsko (JIRA)
Peter Bacsko created OOZIE-3111:
---

 Summary: [Umbrella] Fix flaky tests in Oozie
 Key: OOZIE-3111
 URL: https://issues.apache.org/jira/browse/OOZIE-3111
 Project: Oozie
  Issue Type: Bug
Reporter: Peter Bacsko


In Oozie, we've had a number or flaky tests for quite a while. In order to have 
successful builds, we circumvented the problem by re-running failed tests. But 
this is not a good long-term solution.

This JIRA tracks the tests that are currently flaky. We should address each of 
these tests to have stable builds.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (OOZIE-2897) LauncherAM should support ACLs

2017-11-07 Thread Peter Bacsko (JIRA)

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

Peter Bacsko commented on OOZIE-2897:
-

Thanks [~gezapeti], committed to master.

> LauncherAM should support ACLs
> --
>
> Key: OOZIE-2897
> URL: https://issues.apache.org/jira/browse/OOZIE-2897
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2897-001.patch, OOZIE-2897-002.patch, 
> OOZIE-2897-003.patch, OOZIE-2897-004.patch, OOZIE-2897-005.patch, 
> OOZIE-2897-006.patch
>
>
> In MapReduce, you can define ACL-related properties:
> {noformat}
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modify-job
> {noformat}
> {{acl-view-job}} defines a list of users/groups who can retrieve the job 
> statistics. {{acl-modify-job}} defines a list of users/groups who can kill a 
> job or adjust the priority of it.
> Docs: 
> https://hadoop.apache.org/docs/r1.2.1/mapred_tutorial.html#Job+Authorization
> In YARN, we can provide backward compatibility for these properties. Example 
> code:
> {code}
> Map acls = new HashMap String>();
> acls.put(ApplicationAccessType.MODIFY_APP, "*");
> acls.put(ApplicationAccessType.VIEW_APP, "*");
> amContainer.setApplicationACLs(acls);
> {code}
> This has to be done before application submission. We have to do what 
> YARNRunner.java does: 
> https://github.com/apache/hadoop/blob/3721cfe1fbd98c5b6aa46aefdfcf62276c28c4a4/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/main/java/org/apache/hadoop/mapred/YARNRunner.java#L502-L507
>  
> We should also ensure the compatibility with the properties of:
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modfy-job



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (OOZIE-2964) Add -Xdoclint:none to javadoc opts to avoid warnings

2017-11-07 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-2964:
--

Testing JIRA OOZIE-2964

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch does not add/modify any testcase
{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:red}WARNING{color}: the current HEAD has 77 Javadoc warning(s)
{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 [server].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [docs].
. {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{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/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/hive].
. {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/spark].
{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: 2049
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

.Tests failing with errors:
.  

{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}

{color:red}. There is at least one warning, please check{color}

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

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

> Add -Xdoclint:none to javadoc opts to avoid warnings
> 
>
> Key: OOZIE-2964
> URL: https://issues.apache.org/jira/browse/OOZIE-2964
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
> Environment: java version "1.8.0_51"
> Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
> Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
> Mac OSX 10.12.5
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2964-0.patch, OOZIE-2964-2.patch
>
>
> steps to reproduce
> {noformat}
> ./bin/mkdistro.sh -DskipTests=true -DtargetJavaVersion=1.8 -DjavaVersion=1.8
> {noformat}
> Refer to the generated Javadoc files in 
> '/Users/aervits/NetBeansProjects/OOZIE-AbstractJavadocMojo/oozie/core/target/site/apidocs'
>  dir.
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:5163)
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:2075)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:130)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:318)
> at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoE

Failed: OOZIE-2964 PreCommit Build #189

2017-11-07 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/OOZIE-2964
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/189/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.55 MB...]
+1 There are no new bugs found in total.
 +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 [core].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [examples].
 +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/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/hive].
 +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/spark].
+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: 2049
Tests failed: 1
Tests errors: 0

The patch failed the following testcases:

  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

Tests failing with errors:
  

+1 DISTRO
+1 distro tarball builds with the patch 


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

 There is at least one warning, please check

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

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

  % 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
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100 3706k  100 3706k0 0  3813k  0 --:--:-- --:--:-- --:--:-- 6177k
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-2964
Archiving artifacts
[Fast Archiver] Compressed 1.72 MB of artifacts by 38.1% relative to #164
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  
org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup

Error Message:
expected: but was:

Stack Trace:
junit.framework.AssertionFailedError: expected: 
but was:
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:86)
at junit.framework.TestCase.assertEquals(TestCase.java:253)
at 
org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup(TestCoordMaterializeTransitionXCommand.java:582)
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:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run

[jira] [Commented] (OOZIE-3101) Oozie should add error message to the response body

2017-11-07 Thread Rohini Palaniswamy (JIRA)

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

Rohini Palaniswamy commented on OOZIE-3101:
---

+1

> Oozie should add error message to the response body
> ---
>
> Key: OOZIE-3101
> URL: https://issues.apache.org/jira/browse/OOZIE-3101
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-3101-1.patch, OOZIE-3101-2.patch, 
> OOZIE-3101-3.patch, OOZIE-3101-4.patch, OOZIE-3101-5.patch
>
>
> For web service APIs, currently Oozie adds error message in a custom response 
> header which is parsed out by the OozieClient. Oozie should also put error 
> message in the response body so that clients like curl can display the error 
> message to users without having to turn on verbose output



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (OOZIE-3101) Oozie should add error message to the response body

2017-11-07 Thread Satish Subhashrao Saley (JIRA)

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

Satish Subhashrao Saley updated OOZIE-3101:
---
Attachment: OOZIE-3101-5.patch

Updating patch with changes to failed test case.

> Oozie should add error message to the response body
> ---
>
> Key: OOZIE-3101
> URL: https://issues.apache.org/jira/browse/OOZIE-3101
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-3101-1.patch, OOZIE-3101-2.patch, 
> OOZIE-3101-3.patch, OOZIE-3101-4.patch, OOZIE-3101-5.patch
>
>
> For web service APIs, currently Oozie adds error message in a custom response 
> header which is parsed out by the OozieClient. Oozie should also put error 
> message in the response body so that clients like curl can display the error 
> message to users without having to turn on verbose output



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Re: Review Request 63626: OOZIE-3001 core library has many instances of warnings with trailing spaces and lines longer than 132 chars

2017-11-07 Thread András Piros via Review Board

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




core/src/main/java/org/apache/oozie/action/email/EmailActionExecutor.java
Lines 220 (patched)


Incorrect number of white spaces. Should be 8 more than previous line.



core/src/main/java/org/apache/oozie/action/email/EmailActionExecutor.java
Lines 223 (patched)


Incorrect number of white spaces. Should be 8 more than previous line.



core/src/main/java/org/apache/oozie/action/email/EmailActionExecutor.java
Lines 298 (patched)


Incorrect number of white spaces. Should be 8 more than previous line.



core/src/main/java/org/apache/oozie/action/email/EmailActionExecutor.java
Lines 301 (patched)


Incorrect number of white spaces. Should be 8 more than previous line.



core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java
Lines 667 (patched)


Incorrect number of white spaces. Should be 8 more than previous line.



core/src/main/java/org/apache/oozie/command/bundle/BundleJobResumeXCommand.java
Lines 69-70 (patched)


Incorrect number of white spaces. Should be 8 more than previous line.



core/src/main/java/org/apache/oozie/command/bundle/BundleJobResumeXCommand.java
Lines 126 (patched)


Incorrect number of white spaces. Should be 8 more than previous line.



core/src/main/java/org/apache/oozie/command/bundle/BundleJobResumeXCommand.java
Lines 186 (patched)


Incorrect number of white spaces. Should be 8 more than previous line.



core/src/main/java/org/apache/oozie/command/bundle/BundleKillXCommand.java
Lines 109-110 (original), 111-113 (patched)


Each parameter on new line would be more readable.


- András Piros


On Nov. 7, 2017, 3:19 p.m., Artem Ervits wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63626/
> ---
> 
> (Updated Nov. 7, 2017, 3:19 p.m.)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-3001 core library has many instances of warnings with trailing spaces 
> and lines longer than 132 chars
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/action/email/EmailActionExecutor.java 
> d9417535 
>   core/src/main/java/org/apache/oozie/action/hadoop/HCatCredentials.java 
> 52abbf17 
>   core/src/main/java/org/apache/oozie/action/hadoop/HbaseCredentials.java 
> 22b6dc9f 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> 23e1f69e 
>   core/src/main/java/org/apache/oozie/command/bundle/BundleJobException.java 
> 05e526ed 
>   
> core/src/main/java/org/apache/oozie/command/bundle/BundleJobResumeXCommand.java
>  2e3671df 
>   core/src/main/java/org/apache/oozie/command/bundle/BundleKillXCommand.java 
> 1516ec32 
> 
> 
> Diff: https://reviews.apache.org/r/63626/diff/1/
> 
> 
> Testing
> ---
> 
> yes
> 
> 
> Thanks,
> 
> Artem Ervits
> 
>



[jira] [Commented] (OOZIE-3022) fix for warning has no file and won't be listed in dependency files details

2017-11-07 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-3022:
--

Testing JIRA OOZIE-3022

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch does not add/modify any testcase
{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:red}WARNING{color}: the current HEAD has 77 Javadoc warning(s)
{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 [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:red}-1 TESTS{color}
.Tests run: 2049
.Tests failed: 1
.Tests errors: 1

.The patch failed the following testcases:

.  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

.Tests failing with errors:
.  testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation)

{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}

{color:red}. There is at least one warning, please check{color}

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

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

> fix for warning has no file and won't be listed in dependency files details
> ---
>
> Key: OOZIE-3022
> URL: https://issues.apache.org/jira/browse/OOZIE-3022
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
> Environment: Maven: 3.5.0
> Java: 1.8.0_141
> latest commit: 01826102302e8c62f7b5bf2156aa2c0bb1c84c9e
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-3022-2.patch, OOZIE-3022.patch
>
>
> during build getting warning
> {noformat}
> Artifact com.sun:tools:jar:1.7 has no file and won't be listed in dependency 
> files details
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Failed: OOZIE-3022 PreCommit Build #187

2017-11-07 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/OOZIE-3022
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/187/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.60 MB...]
+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 [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: 2049
Tests failed: 1
Tests errors: 1

The patch failed the following testcases:

  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

Tests failing with errors:
  testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation)

+1 DISTRO
+1 distro tarball builds with the patch 


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

 There is at least one warning, please check

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

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

  % 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  0 
00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
100 3706k  100 3706k0 0  2918k  0  0:00:01  0:00:01 --:--:-- 2918k
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-3022
Archiving artifacts
[Fast Archiver] Compressed 1.81 MB of artifacts by 32.8% relative to #164
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
2 tests failed.
FAILED:  org.apache.oozie.util.TestMetricsInstrumentation.testJMXInstrumentation

Error Message:
Unable to open socket file: target process not responding or HotSpot VM not 
loaded

Stack Trace:
com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file: 
target process not responding or HotSpot VM not loaded
at 
sun.tools.attach.LinuxVirtualMachine.(LinuxVirtualMachine.java:106)
at 
sun.tools.attach.LinuxAttachProvider.attachVirtualMachine(LinuxAttachProvider.java:78)
at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:250)
at 
org.apache.oozie.util.TestMetricsInstrumentation.testJMXInstrumentation(TestMetricsInstrumentation.java:235)
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:1149)
at 
java.util

[jira] [Updated] (OOZIE-2964) Add -Xdoclint:none to javadoc opts to avoid warnings

2017-11-07 Thread Artem Ervits (JIRA)

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

Artem Ervits updated OOZIE-2964:

Attachment: OOZIE-2964-2.patch

> Add -Xdoclint:none to javadoc opts to avoid warnings
> 
>
> Key: OOZIE-2964
> URL: https://issues.apache.org/jira/browse/OOZIE-2964
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
> Environment: java version "1.8.0_51"
> Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
> Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
> Mac OSX 10.12.5
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2964-0.patch, OOZIE-2964-2.patch
>
>
> steps to reproduce
> {noformat}
> ./bin/mkdistro.sh -DskipTests=true -DtargetJavaVersion=1.8 -DjavaVersion=1.8
> {noformat}
> Refer to the generated Javadoc files in 
> '/Users/aervits/NetBeansProjects/OOZIE-AbstractJavadocMojo/oozie/core/target/site/apidocs'
>  dir.
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:5163)
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:2075)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:130)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:318)
> at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> 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:497)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (OOZIE-2964) Add -Xdoclint:none to javadoc opts to avoid warnings

2017-11-07 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-2964:
--

Testing JIRA OOZIE-2964

Cleaning local git workspace

> Add -Xdoclint:none to javadoc opts to avoid warnings
> 
>
> Key: OOZIE-2964
> URL: https://issues.apache.org/jira/browse/OOZIE-2964
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
> Environment: java version "1.8.0_51"
> Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
> Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
> Mac OSX 10.12.5
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2964-0.patch
>
>
> steps to reproduce
> {noformat}
> ./bin/mkdistro.sh -DskipTests=true -DtargetJavaVersion=1.8 -DjavaVersion=1.8
> {noformat}
> Refer to the generated Javadoc files in 
> '/Users/aervits/NetBeansProjects/OOZIE-AbstractJavadocMojo/oozie/core/target/site/apidocs'
>  dir.
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:5163)
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:2075)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:130)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:318)
> at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> 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:497)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Failed: OOZIE-2964 PreCommit Build #188

2017-11-07 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/OOZIE-2964
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/188/

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by remote host 127.0.0.1
[EnvInject] - Loading node environment variables.
Building remotely on H13 (couchdbtest Hadoop xenial) in workspace 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build@2
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 53edaaf619d274e9c0ac1c4848c0290b0429a30f 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 53edaaf619d274e9c0ac1c4848c0290b0429a30f
Commit message: "OOZIE-2962 bump maven-javadoc-plugin to 2.10.4 (dbist13 via 
andras.piros)"
 > git rev-list 53edaaf619d274e9c0ac1c4848c0290b0429a30f # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
No emails were triggered.
[PreCommit-OOZIE-Build@2] $ /bin/bash /tmp/jenkins2472910420086013381.sh
OOZIE-2964
rm: cannot remove 'distro/downloads/*': No such file or directory
rm: invalid option -- '.'
Try 'rm --help' for more information.

Testing JIRA OOZIE-2964

  % 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 --:--:-- --:--:-- --:--:-- 0100 
158810 158810 0  15238  0 --:--:--  0:00:01 --:--:-- 15226100 
916890 916890 0  81131  0 --:--:--  0:00:01 --:--:-- 81140
OOZIE-2964 is not "Patch Available".  Exiting.

  % 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
  0 3706k0 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100 3706k  100 3706k0 0  3338k  0  0:00:01  0:00:01 --:--:-- 17.2M
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-2964
Archiving artifacts
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Comment Edited] (OOZIE-2964) Add -Xdoclint:none to javadoc opts to avoid warnings

2017-11-07 Thread Artem Ervits (JIRA)

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

Artem Ervits edited comment on OOZIE-2964 at 11/7/17 3:47 PM:
--

[~andras.piros] thanks for review, I added your properties and the patch did 
not fix the apidoc error above. I agree that with my patch we lose a lot of 
visibility and better to address the original issue than hide everything. I am 
strapped for time now and cannot work on this but I will dig deeper into what 
is going on. I am attaching my patch with rebase just for continuity.


was (Author: dbist13):
[~andras.piros] thanks for review, attaching new patch based on latest master

> Add -Xdoclint:none to javadoc opts to avoid warnings
> 
>
> Key: OOZIE-2964
> URL: https://issues.apache.org/jira/browse/OOZIE-2964
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
> Environment: java version "1.8.0_51"
> Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
> Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
> Mac OSX 10.12.5
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2964-0.patch
>
>
> steps to reproduce
> {noformat}
> ./bin/mkdistro.sh -DskipTests=true -DtargetJavaVersion=1.8 -DjavaVersion=1.8
> {noformat}
> Refer to the generated Javadoc files in 
> '/Users/aervits/NetBeansProjects/OOZIE-AbstractJavadocMojo/oozie/core/target/site/apidocs'
>  dir.
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:5163)
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:2075)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:130)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:318)
> at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> 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:497)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (OOZIE-2964) Add -Xdoclint:none to javadoc opts to avoid warnings

2017-11-07 Thread Artem Ervits (JIRA)

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

Artem Ervits updated OOZIE-2964:

Attachment: (was: OOZIE-2964-1.patch)

> Add -Xdoclint:none to javadoc opts to avoid warnings
> 
>
> Key: OOZIE-2964
> URL: https://issues.apache.org/jira/browse/OOZIE-2964
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
> Environment: java version "1.8.0_51"
> Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
> Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
> Mac OSX 10.12.5
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2964-0.patch
>
>
> steps to reproduce
> {noformat}
> ./bin/mkdistro.sh -DskipTests=true -DtargetJavaVersion=1.8 -DjavaVersion=1.8
> {noformat}
> Refer to the generated Javadoc files in 
> '/Users/aervits/NetBeansProjects/OOZIE-AbstractJavadocMojo/oozie/core/target/site/apidocs'
>  dir.
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:5163)
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:2075)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:130)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:318)
> at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> 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:497)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (OOZIE-2964) Add -Xdoclint:none to javadoc opts to avoid warnings

2017-11-07 Thread Artem Ervits (JIRA)

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

Artem Ervits updated OOZIE-2964:

Attachment: OOZIE-2964-1.patch

[~andras.piros] thanks for review, attaching new patch based on latest master

> Add -Xdoclint:none to javadoc opts to avoid warnings
> 
>
> Key: OOZIE-2964
> URL: https://issues.apache.org/jira/browse/OOZIE-2964
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
> Environment: java version "1.8.0_51"
> Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
> Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
> Mac OSX 10.12.5
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2964-0.patch, OOZIE-2964-1.patch
>
>
> steps to reproduce
> {noformat}
> ./bin/mkdistro.sh -DskipTests=true -DtargetJavaVersion=1.8 -DjavaVersion=1.8
> {noformat}
> Refer to the generated Javadoc files in 
> '/Users/aervits/NetBeansProjects/OOZIE-AbstractJavadocMojo/oozie/core/target/site/apidocs'
>  dir.
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:5163)
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:2075)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:130)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:318)
> at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> 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:497)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (OOZIE-3110) Supported special characters in oozie db password

2017-11-07 Thread alex (JIRA)

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

alex updated OOZIE-3110:

Affects Version/s: 4.1.0

> Supported special characters in oozie db password
> -
>
> Key: OOZIE-3110
> URL: https://issues.apache.org/jira/browse/OOZIE-3110
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 4.1.0
>Reporter: alex
>
> Hi,
> I am using a cluster where, Mariadb is used as the metastore.
> The password for oozie user in mariadb is "abcrd_#"
> Oozie service does not start with this password. I get the below error:
> REASON: org.apache.oozie.service.ServiceException: E0103: Could not load 
> service classes, Cannot create PoolableConnectionFactory (Access denied for 
> user 'oozie'@'cdlk-app-node.localdomain' (using password: YES))
> So I wanted to know, what special characters are supported in password ?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (OOZIE-3110) Supported special characters in oozie db password

2017-11-07 Thread alex (JIRA)
alex created OOZIE-3110:
---

 Summary: Supported special characters in oozie db password
 Key: OOZIE-3110
 URL: https://issues.apache.org/jira/browse/OOZIE-3110
 Project: Oozie
  Issue Type: Improvement
Reporter: alex


Hi,

I am using a cluster where, Mariadb is used as the metastore.
The password for oozie user in mariadb is "abcrd_#"

Oozie service does not start with this password. I get the below error:

REASON: org.apache.oozie.service.ServiceException: E0103: Could not load 
service classes, Cannot create PoolableConnectionFactory (Access denied for 
user 'oozie'@'cdlk-app-node.localdomain' (using password: YES))

So I wanted to know, what special characters are supported in password ?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (OOZIE-3001) core library has many instances of warnings with trailing spaces and lines longer than 132 chars

2017-11-07 Thread Artem Ervits (JIRA)

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

Artem Ervits commented on OOZIE-3001:
-

[~andras.piros] please review https://reviews.apache.org/r/63626/

> core library has many instances of warnings with trailing spaces and lines 
> longer than 132 chars
> 
>
> Key: OOZIE-3001
> URL: https://issues.apache.org/jira/browse/OOZIE-3001
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>  Labels: newbie
> Attachments: OOZIE-3001-2.patch
>
>
> {noformat}
> /Users/aervits/NetBeansProjects/minioozie/oozie/core/src/main/java/org/apache/oozie/action/email/EmailActionExecutor.java:219:
>  warning: Line is longer than 132 characters.
> /Users/aervits/NetBeansProjects/minioozie/oozie/core/src/main/java/org/apache/oozie/action/email/EmailActionExecutor.java:297:
>  warning: Line is longer than 132 characters.
> /Users/aervits/NetBeansProjects/minioozie/oozie/core/src/main/java/org/apache/oozie/action/hadoop/HbaseCredentials.java:40:
>  warning: Line is longer than 132 characters.
> /Users/aervits/NetBeansProjects/minioozie/oozie/core/src/main/java/org/apache/oozie/action/hadoop/HbaseCredentials.java:45:
>  warning: Line is longer than 132 characters.
> /Users/aervits/NetBeansProjects/minioozie/oozie/core/src/main/java/org/apache/oozie/action/hadoop/HCatCredentials.java:35:
>  warning: Line is longer than 132 characters.
> /Users/aervits/NetBeansProjects/minioozie/oozie/core/src/main/java/org/apache/oozie/action/hadoop/HCatCredentials.java:51:
>  warning: Line is longer than 132 characters.
> /Users/aervits/NetBeansProjects/minioozie/oozie/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java:643:
>  warning: Line is longer than 132 characters.
> /Users/aervits/NetBeansProjects/minioozie/oozie/core/src/main/java/org/apache/oozie/BundleActionBean.java:46:
>  warning: Line is longer than 132 characters.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Review Request 63626: OOZIE-3001 core library has many instances of warnings with trailing spaces and lines longer than 132 chars

2017-11-07 Thread Artem Ervits

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

Review request for oozie and András Piros.


Repository: oozie-git


Description
---

OOZIE-3001 core library has many instances of warnings with trailing spaces and 
lines longer than 132 chars


Diffs
-

  core/src/main/java/org/apache/oozie/action/email/EmailActionExecutor.java 
d9417535 
  core/src/main/java/org/apache/oozie/action/hadoop/HCatCredentials.java 
52abbf17 
  core/src/main/java/org/apache/oozie/action/hadoop/HbaseCredentials.java 
22b6dc9f 
  core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
23e1f69e 
  core/src/main/java/org/apache/oozie/command/bundle/BundleJobException.java 
05e526ed 
  
core/src/main/java/org/apache/oozie/command/bundle/BundleJobResumeXCommand.java 
2e3671df 
  core/src/main/java/org/apache/oozie/command/bundle/BundleKillXCommand.java 
1516ec32 


Diff: https://reviews.apache.org/r/63626/diff/1/


Testing
---

yes


Thanks,

Artem Ervits



[jira] [Commented] (OOZIE-2897) LauncherAM should support ACLs

2017-11-07 Thread Peter Cseh (JIRA)

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

Peter Cseh commented on OOZIE-2897:
---

Test failure seems unrelated. +1!

> LauncherAM should support ACLs
> --
>
> Key: OOZIE-2897
> URL: https://issues.apache.org/jira/browse/OOZIE-2897
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2897-001.patch, OOZIE-2897-002.patch, 
> OOZIE-2897-003.patch, OOZIE-2897-004.patch, OOZIE-2897-005.patch, 
> OOZIE-2897-006.patch
>
>
> In MapReduce, you can define ACL-related properties:
> {noformat}
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modify-job
> {noformat}
> {{acl-view-job}} defines a list of users/groups who can retrieve the job 
> statistics. {{acl-modify-job}} defines a list of users/groups who can kill a 
> job or adjust the priority of it.
> Docs: 
> https://hadoop.apache.org/docs/r1.2.1/mapred_tutorial.html#Job+Authorization
> In YARN, we can provide backward compatibility for these properties. Example 
> code:
> {code}
> Map acls = new HashMap String>();
> acls.put(ApplicationAccessType.MODIFY_APP, "*");
> acls.put(ApplicationAccessType.VIEW_APP, "*");
> amContainer.setApplicationACLs(acls);
> {code}
> This has to be done before application submission. We have to do what 
> YARNRunner.java does: 
> https://github.com/apache/hadoop/blob/3721cfe1fbd98c5b6aa46aefdfcf62276c28c4a4/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/main/java/org/apache/hadoop/mapred/YARNRunner.java#L502-L507
>  
> We should also ensure the compatibility with the properties of:
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modfy-job



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (OOZIE-3022) fix for warning has no file and won't be listed in dependency files details

2017-11-07 Thread Artem Ervits (JIRA)

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

Artem Ervits updated OOZIE-3022:

Attachment: OOZIE-3022-2.patch

[~andras.piros] and [~gezapeti] thanks for your mentorship, the exclusion 
worked, the other option didn't. I don't see a message with the attached patch.

> fix for warning has no file and won't be listed in dependency files details
> ---
>
> Key: OOZIE-3022
> URL: https://issues.apache.org/jira/browse/OOZIE-3022
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
> Environment: Maven: 3.5.0
> Java: 1.8.0_141
> latest commit: 01826102302e8c62f7b5bf2156aa2c0bb1c84c9e
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.0.0
>
> Attachments: OOZIE-3022-2.patch, OOZIE-3022.patch
>
>
> during build getting warning
> {noformat}
> Artifact com.sun:tools:jar:1.7 has no file and won't be listed in dependency 
> files details
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Re: Review Request 63327: OOZIE-2897 LauncherAM should support ACLs

2017-11-07 Thread Peter Cseh via Review Board

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


Ship it!




Ship It!

- Peter Cseh


On Nov. 7, 2017, 12:36 p.m., Peter Bacsko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63327/
> ---
> 
> (Updated Nov. 7, 2017, 12:36 p.m.)
> 
> 
> Review request for oozie, András Piros, Attila Sasvari, Peter Cseh, and 
> Robert Kanter.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/OOZIE-2897
> 
> 
> Diffs
> -
> 
>   client/src/main/resources/oozie-common-1.0.xsd ddae91224 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> 6a25e5c89 
>   core/src/main/java/org/apache/oozie/action/hadoop/YarnACLHandler.java 
> PRE-CREATION 
>   
> core/src/main/java/org/apache/oozie/workflow/lite/LauncherConfigHandler.java 
> c36774239 
>   core/src/main/resources/oozie-default.xml 8285df0a7 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/ActionExecutorTestCase.java 
> 36b302667 
>   core/src/test/java/org/apache/oozie/action/hadoop/LauncherMainTester.java 
> 43c71b0ad 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> adb2168ca 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherConfigurationInjector.java
>  4c5b0f972 
>   core/src/test/java/org/apache/oozie/action/hadoop/TestYarnACLHandler.java 
> PRE-CREATION 
>   core/src/test/java/org/apache/oozie/service/TestSchemaService.java 
> 940868aeb 
>   core/src/test/java/org/apache/oozie/test/XTestCase.java 912c3f316 
>   
> core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java
>  a361078ac 
>   core/src/test/resources/fair-scheduler-alloc.xml PRE-CREATION 
>   core/src/test/resources/wf-schema-global-launcherconf.xml 9cd4f6c37 
> 
> 
> Diff: https://reviews.apache.org/r/63327/diff/4/
> 
> 
> Testing
> ---
> 
> - Unit test added
> - Verified on a 4-node cluster
> 
> 
> Thanks,
> 
> Peter Bacsko
> 
>



[jira] [Commented] (OOZIE-2962) bump maven-javadoc-plugin to 2.10.4

2017-11-07 Thread Andras Piros (JIRA)

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

Andras Piros commented on OOZIE-2962:
-

Committed to master.

> bump maven-javadoc-plugin to 2.10.4
> ---
>
> Key: OOZIE-2962
> URL: https://issues.apache.org/jira/browse/OOZIE-2962
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
>  Labels: newbie
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2962-0.patch
>
>
> there are a few errors in latest builds
> {noformat}
> Error fetching link: 
> /home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/sharelib/hcatalog/target/site/apidocs/package-list
> {noformat}
> that can be downgraded to warning with latest maven-javadoc-plugin as well as 
> other fixes to the plugin, currently used 2.10.3 was released in 2015, 2.10.4 
> has a few fixes on top of that and was released in 2016.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (OOZIE-2962) bump maven-javadoc-plugin to 2.10.4

2017-11-07 Thread Artem Ervits (JIRA)

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

Artem Ervits commented on OOZIE-2962:
-

[~andras.piros] thanks for review, failing test due to 
https://issues.apache.org/jira/browse/OOZIE-2726 and unrelated.

> bump maven-javadoc-plugin to 2.10.4
> ---
>
> Key: OOZIE-2962
> URL: https://issues.apache.org/jira/browse/OOZIE-2962
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
>  Labels: newbie
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2962-0.patch
>
>
> there are a few errors in latest builds
> {noformat}
> Error fetching link: 
> /home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/sharelib/hcatalog/target/site/apidocs/package-list
> {noformat}
> that can be downgraded to warning with latest maven-javadoc-plugin as well as 
> other fixes to the plugin, currently used 2.10.3 was released in 2015, 2.10.4 
> has a few fixes on top of that and was released in 2016.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (OOZIE-2962) bump maven-javadoc-plugin to 2.10.4

2017-11-07 Thread Artem Ervits (JIRA)

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

Artem Ervits updated OOZIE-2962:

Fix Version/s: (was: 5.0.0)
   (was: trunk)
   5.0.0b1

> bump maven-javadoc-plugin to 2.10.4
> ---
>
> Key: OOZIE-2962
> URL: https://issues.apache.org/jira/browse/OOZIE-2962
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
>  Labels: newbie
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2962-0.patch
>
>
> there are a few errors in latest builds
> {noformat}
> Error fetching link: 
> /home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/sharelib/hcatalog/target/site/apidocs/package-list
> {noformat}
> that can be downgraded to warning with latest maven-javadoc-plugin as well as 
> other fixes to the plugin, currently used 2.10.3 was released in 2015, 2.10.4 
> has a few fixes on top of that and was released in 2016.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (OOZIE-2726) Flaky test due to daylight saving changes

2017-11-07 Thread Artem Ervits (JIRA)

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

Artem Ervits updated OOZIE-2726:

Priority: Blocker  (was: Minor)

> Flaky test due to daylight saving changes
> -
>
> Key: OOZIE-2726
> URL: https://issues.apache.org/jira/browse/OOZIE-2726
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: OOZIE-2726-1.patch, OOZIE-2726-2.patch, 
> OOZIE-2726-3.patch, OOZIE-2726-4.patch, OOZIE-2726-5.patch
>
>
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup
> {code}
> Error Message
> expected: but was:
> Stacktrace
> junit.framework.AssertionFailedError: expected: 
> but was:
>   at junit.framework.Assert.fail(Assert.java:50)
>   at junit.framework.Assert.failNotEquals(Assert.java:287)
>   at junit.framework.Assert.assertEquals(Assert.java:67)
>   at junit.framework.Assert.assertEquals(Assert.java:74)
>   at 
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup(TestCoordMaterializeTransitionXCommand.java:582)
>   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:483)
>   at junit.framework.TestCase.runTest(TestCase.java:168)
>   at junit.framework.TestCase.runBare(TestCase.java:134)
>   at junit.framework.TestResult$1.protect(TestResult.java:110)
>   at junit.framework.TestResult.runProtected(TestResult.java:128)
>   at junit.framework.TestResult.run(TestResult.java:113)
>   at junit.framework.TestCase.run(TestCase.java:124)
>   at junit.framework.TestSuite.runTest(TestSuite.java:243)
>   at junit.framework.TestSuite.run(TestSuite.java:238)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
>   at org.junit.runners.Suite.runChild(Suite.java:128)
>   at org.junit.runners.Suite.runChild(Suite.java:24)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
>   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
(v6.4.14#64029)


Re: Review Request 63327: OOZIE-2897 LauncherAM should support ACLs

2017-11-07 Thread Peter Bacsko via Review Board

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

(Updated nov. 7, 2017, 12:36 du)


Review request for oozie, András Piros, Attila Sasvari, Peter Cseh, and Robert 
Kanter.


Repository: oozie-git


Description
---

https://issues.apache.org/jira/browse/OOZIE-2897


Diffs (updated)
-

  client/src/main/resources/oozie-common-1.0.xsd ddae91224 
  core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
6a25e5c89 
  core/src/main/java/org/apache/oozie/action/hadoop/YarnACLHandler.java 
PRE-CREATION 
  core/src/main/java/org/apache/oozie/workflow/lite/LauncherConfigHandler.java 
c36774239 
  core/src/main/resources/oozie-default.xml 8285df0a7 
  core/src/test/java/org/apache/oozie/action/hadoop/ActionExecutorTestCase.java 
36b302667 
  core/src/test/java/org/apache/oozie/action/hadoop/LauncherMainTester.java 
43c71b0ad 
  core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
adb2168ca 
  
core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherConfigurationInjector.java
 4c5b0f972 
  core/src/test/java/org/apache/oozie/action/hadoop/TestYarnACLHandler.java 
PRE-CREATION 
  core/src/test/java/org/apache/oozie/service/TestSchemaService.java 940868aeb 
  core/src/test/java/org/apache/oozie/test/XTestCase.java 912c3f316 
  
core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java
 a361078ac 
  core/src/test/resources/fair-scheduler-alloc.xml PRE-CREATION 
  core/src/test/resources/wf-schema-global-launcherconf.xml 9cd4f6c37 


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

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


Testing
---

- Unit test added
- Verified on a 4-node cluster


Thanks,

Peter Bacsko



[jira] [Commented] (OOZIE-2897) LauncherAM should support ACLs

2017-11-07 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-2897:
--

Testing JIRA OOZIE-2897

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 does adds/modifies 10 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:red}WARNING{color}: the current HEAD has 77 Javadoc warning(s)
{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 [server].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [docs].
. {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{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/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/hive].
. {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/spark].
{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: 2054
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

.Tests failing with errors:
.  

{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}

{color:red}. There is at least one warning, please check{color}

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

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

> LauncherAM should support ACLs
> --
>
> Key: OOZIE-2897
> URL: https://issues.apache.org/jira/browse/OOZIE-2897
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2897-001.patch, OOZIE-2897-002.patch, 
> OOZIE-2897-003.patch, OOZIE-2897-004.patch, OOZIE-2897-005.patch, 
> OOZIE-2897-006.patch
>
>
> In MapReduce, you can define ACL-related properties:
> {noformat}
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modify-job
> {noformat}
> {{acl-view-job}} defines a list of users/groups who can retrieve the job 
> statistics. {{acl-modify-job}} defines a list of users/groups who can kill a 
> job or adjust the priority of it.
> Docs: 
> https://hadoop.apache.org/docs/r1.2.1/mapred_tutorial.html#Job+Authorization
> In YARN, we can provide backward compatibility for these properties. Example 
> code:
> {code}
> Map acls = new HashMap String>();
> acls.put(ApplicationAccessType.MODIFY_APP, "*");
> acls.put(ApplicationAccessType.VIEW_APP, "*");
> amContainer.setApplicationACLs(acls);
> {code}
> This has to be done before application submission. We have to do what 
> YARNRunner.java does: 
> https://github.com/apache/hadoop/blob/3721cfe1fbd98c5b6aa46aefdfcf62276c28c4a4/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/main/java/org/apache/hadoop/mapred/YARNRunner.java#L502-L507
>  
> We should also ensure the compatibility with the properties of:
> mapreduce.job

Failed: OOZIE-2897 PreCommit Build #186

2017-11-07 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/OOZIE-2897
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/186/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.61 MB...]
+1 There are no new bugs found in total.
 +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 [core].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [examples].
 +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/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/hive].
 +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/spark].
+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: 2054
Tests failed: 1
Tests errors: 0

The patch failed the following testcases:

  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

Tests failing with errors:
  

+1 DISTRO
+1 distro tarball builds with the patch 


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

 There is at least one warning, please check

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

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

  % 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
  0 3706k0 101360 0  13563  0  0:04:39 --:--:--  0:04:39 
13563100 3706k  100 3706k0 0  3801k  0 --:--:-- --:--:-- --:--:-- 
15.9M
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-2897
Archiving artifacts
[Fast Archiver] Compressed 1.81 MB of artifacts by 32.8% relative to #164
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  
org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup

Error Message:
expected: but was:

Stack Trace:
junit.framework.AssertionFailedError: expected: 
but was:
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:86)
at junit.framework.TestCase.assertEquals(TestCase.java:253)
at 
org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup(TestCoordMaterializeTransitionXCommand.java:582)
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:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.ru

[jira] [Commented] (OOZIE-2962) bump maven-javadoc-plugin to 2.10.4

2017-11-07 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-2962:
--

Testing JIRA OOZIE-2962

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch does not add/modify any testcase
{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:red}WARNING{color}: the current HEAD has 77 Javadoc warning(s)
{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 [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:red}-1 TESTS{color}
.Tests run: 2049
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

.Tests failing with errors:
.  

{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}

{color:red}. There is at least one warning, please check{color}

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

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

> bump maven-javadoc-plugin to 2.10.4
> ---
>
> Key: OOZIE-2962
> URL: https://issues.apache.org/jira/browse/OOZIE-2962
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
>  Labels: newbie
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2962-0.patch
>
>
> there are a few errors in latest builds
> {noformat}
> Error fetching link: 
> /home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/sharelib/hcatalog/target/site/apidocs/package-list
> {noformat}
> that can be downgraded to warning with latest maven-javadoc-plugin as well as 
> other fixes to the plugin, currently used 2.10.3 was released in 2015, 2.10.4 
> has a few fixes on top of that and was released in 2016.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Failed: OOZIE-2962 PreCommit Build #185

2017-11-07 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/OOZIE-2962
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/185/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.60 MB...]
+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 [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: 2049
Tests failed: 1
Tests errors: 0

The patch failed the following testcases:

  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

Tests failing with errors:
  

+1 DISTRO
+1 distro tarball builds with the patch 


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

 There is at least one warning, please check

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

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

  % 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
  2 3706k2 976200 0   138k  0  0:00:26 --:--:--  0:00:26  
138k100 3706k  100 3706k0 0  4523k  0 --:--:-- --:--:-- --:--:-- 
26.9M
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-2962
Archiving artifacts
[Fast Archiver] Compressed 1.81 MB of artifacts by 36.3% relative to #164
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  
org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup

Error Message:
expected: but was:

Stack Trace:
junit.framework.AssertionFailedError: expected: 
but was:
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:86)
at junit.framework.TestCase.assertEquals(TestCase.java:253)
at 
org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup(TestCoordMaterializeTransitionXCommand.java:582)
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:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.ru

[jira] [Commented] (OOZIE-2962) bump maven-javadoc-plugin to 2.10.4

2017-11-07 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-2962:
--

Testing JIRA OOZIE-2962

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch does not add/modify any testcase
{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:red}WARNING{color}: the current HEAD has 77 Javadoc warning(s)
{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 [client].
. {color:green}+1{color} There are no new bugs found in [docs].
. {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/hive2].
. {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/hcatalog].
. {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/distcp].
. {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 [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: 2049
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

.Tests failing with errors:
.  

{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}

{color:red}. There is at least one warning, please check{color}

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

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

> bump maven-javadoc-plugin to 2.10.4
> ---
>
> Key: OOZIE-2962
> URL: https://issues.apache.org/jira/browse/OOZIE-2962
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
>  Labels: newbie
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2962-0.patch
>
>
> there are a few errors in latest builds
> {noformat}
> Error fetching link: 
> /home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/sharelib/hcatalog/target/site/apidocs/package-list
> {noformat}
> that can be downgraded to warning with latest maven-javadoc-plugin as well as 
> other fixes to the plugin, currently used 2.10.3 was released in 2015, 2.10.4 
> has a few fixes on top of that and was released in 2016.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Failed: OOZIE-2962 PreCommit Build #184

2017-11-07 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/OOZIE-2962
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/184/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.60 MB...]
+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 [client].
 +1 There are no new bugs found in [docs].
 +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/hive2].
 +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/hcatalog].
 +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/distcp].
 +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 [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: 2049
Tests failed: 1
Tests errors: 0

The patch failed the following testcases:

  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

Tests failing with errors:
  

+1 DISTRO
+1 distro tarball builds with the patch 


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

 There is at least one warning, please check

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

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

  % 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
100 3706k  100 3706k0 0  4557k  0 --:--:-- --:--:-- --:--:-- 4557k
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-2962
Archiving artifacts
[Fast Archiver] Compressed 1.81 MB of artifacts by 36.3% relative to #164
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  
org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup

Error Message:
expected: but was:

Stack Trace:
junit.framework.AssertionFailedError: expected: 
but was:
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:86)
at junit.framework.TestCase.assertEquals(TestCase.java:253)
at 
org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup(TestCoordMaterializeTransitionXCommand.java:582)
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:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

[jira] [Commented] (OOZIE-3022) fix for warning has no file and won't be listed in dependency files details

2017-11-07 Thread Andras Piros (JIRA)

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

Andras Piros commented on OOZIE-3022:
-

[~dbist13] thanks for the contribution!

I share [~gezapeti]'s concerns about shadowing more important dependency 
warnings.

What about one of the following instead:
* exclude {{com.sun:tools}} where applicable
{noformat}

tools
com.sun

{noformat}
* explicitly state the {{}} of {{com.sun:tools}} dependency where 
applicable:
{noformat}

   com.sun
   tools
   system
   ${JAVA_HOME}/lib/tools.jar
 
{noformat}

> fix for warning has no file and won't be listed in dependency files details
> ---
>
> Key: OOZIE-3022
> URL: https://issues.apache.org/jira/browse/OOZIE-3022
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
> Environment: Maven: 3.5.0
> Java: 1.8.0_141
> latest commit: 01826102302e8c62f7b5bf2156aa2c0bb1c84c9e
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.0.0
>
> Attachments: OOZIE-3022.patch
>
>
> during build getting warning
> {noformat}
> Artifact com.sun:tools:jar:1.7 has no file and won't be listed in dependency 
> files details
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (OOZIE-3001) core library has many instances of warnings with trailing spaces and lines longer than 132 chars

2017-11-07 Thread Andras Piros (JIRA)

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

Andras Piros commented on OOZIE-3001:
-

[~dbist13] thanks for the contribution!

Can you put the patch to ReviewBoard? Thanks!

> core library has many instances of warnings with trailing spaces and lines 
> longer than 132 chars
> 
>
> Key: OOZIE-3001
> URL: https://issues.apache.org/jira/browse/OOZIE-3001
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>  Labels: newbie
> Attachments: OOZIE-3001-2.patch
>
>
> {noformat}
> /Users/aervits/NetBeansProjects/minioozie/oozie/core/src/main/java/org/apache/oozie/action/email/EmailActionExecutor.java:219:
>  warning: Line is longer than 132 characters.
> /Users/aervits/NetBeansProjects/minioozie/oozie/core/src/main/java/org/apache/oozie/action/email/EmailActionExecutor.java:297:
>  warning: Line is longer than 132 characters.
> /Users/aervits/NetBeansProjects/minioozie/oozie/core/src/main/java/org/apache/oozie/action/hadoop/HbaseCredentials.java:40:
>  warning: Line is longer than 132 characters.
> /Users/aervits/NetBeansProjects/minioozie/oozie/core/src/main/java/org/apache/oozie/action/hadoop/HbaseCredentials.java:45:
>  warning: Line is longer than 132 characters.
> /Users/aervits/NetBeansProjects/minioozie/oozie/core/src/main/java/org/apache/oozie/action/hadoop/HCatCredentials.java:35:
>  warning: Line is longer than 132 characters.
> /Users/aervits/NetBeansProjects/minioozie/oozie/core/src/main/java/org/apache/oozie/action/hadoop/HCatCredentials.java:51:
>  warning: Line is longer than 132 characters.
> /Users/aervits/NetBeansProjects/minioozie/oozie/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java:643:
>  warning: Line is longer than 132 characters.
> /Users/aervits/NetBeansProjects/minioozie/oozie/core/src/main/java/org/apache/oozie/BundleActionBean.java:46:
>  warning: Line is longer than 132 characters.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Failed: OOZIE-2964 PreCommit Build #183

2017-11-07 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/OOZIE-2964
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/183/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 678.32 KB...]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [ 10.160 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [ 11.127 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  7.610 s]
[INFO] Apache Oozie Examples .. SUCCESS [ 11.244 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 12.650 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.098 s]
[INFO] Apache Oozie Docs .. SUCCESS [  4.781 s]
[INFO] Apache Oozie WebApp  SUCCESS [  3.737 s]
[INFO] Apache Oozie Tools . SUCCESS [ 13.598 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  2.527 s]
[INFO] Apache Oozie Server  SUCCESS [ 12.568 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.161 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.828 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 04:04 min
[INFO] Finished at: 2017-11-07T09:48:47Z
[INFO] Final Memory: 644M/1927M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch pom.xml...
error: while searching for:


true
-Xmx1024m -da 
-XX:MaxPermSize=512m


${oozie.test.dir}
localhost

error: patch failed: pom.xml:69
error: pom.xml: patch does not apply
fatal: git diff header lacks filename information when removing 1 leading 
pathname component (line 5)
Patch failed to apply to head of branch

  % 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  0 
00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
100 3706k  100 3706k0 0  3579k  0  0:00:01  0:00:01 --:--:-- 3579k
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-2964
Archiving artifacts
[Fast Archiver] Compressed 844.42 KB of artifacts by 53.1% relative to #164
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Commented] (OOZIE-2964) Add -Xdoclint:none to javadoc opts to avoid warnings

2017-11-07 Thread Andras Piros (JIRA)

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

Andras Piros commented on OOZIE-2964:
-

[~dbist13] can you please rebase to current {{master}}?

> Add -Xdoclint:none to javadoc opts to avoid warnings
> 
>
> Key: OOZIE-2964
> URL: https://issues.apache.org/jira/browse/OOZIE-2964
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
> Environment: java version "1.8.0_51"
> Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
> Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
> Mac OSX 10.12.5
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2964-0.patch
>
>
> steps to reproduce
> {noformat}
> ./bin/mkdistro.sh -DskipTests=true -DtargetJavaVersion=1.8 -DjavaVersion=1.8
> {noformat}
> Refer to the generated Javadoc files in 
> '/Users/aervits/NetBeansProjects/OOZIE-AbstractJavadocMojo/oozie/core/target/site/apidocs'
>  dir.
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:5163)
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:2075)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:130)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:318)
> at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> 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:497)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (OOZIE-2964) Add -Xdoclint:none to javadoc opts to avoid warnings

2017-11-07 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-2964:
--

Testing JIRA OOZIE-2964

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch



> Add -Xdoclint:none to javadoc opts to avoid warnings
> 
>
> Key: OOZIE-2964
> URL: https://issues.apache.org/jira/browse/OOZIE-2964
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
> Environment: java version "1.8.0_51"
> Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
> Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
> Mac OSX 10.12.5
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2964-0.patch
>
>
> steps to reproduce
> {noformat}
> ./bin/mkdistro.sh -DskipTests=true -DtargetJavaVersion=1.8 -DjavaVersion=1.8
> {noformat}
> Refer to the generated Javadoc files in 
> '/Users/aervits/NetBeansProjects/OOZIE-AbstractJavadocMojo/oozie/core/target/site/apidocs'
>  dir.
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:5163)
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:2075)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:130)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:318)
> at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> 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:497)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (OOZIE-2962) bump maven-javadoc-plugin to 2.10.4

2017-11-07 Thread Andras Piros (JIRA)

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

Andras Piros commented on OOZIE-2962:
-

[~dbist13] thanks for the contribution!

+1 (pending Jenkins)

> bump maven-javadoc-plugin to 2.10.4
> ---
>
> Key: OOZIE-2962
> URL: https://issues.apache.org/jira/browse/OOZIE-2962
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
>  Labels: newbie
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2962-0.patch
>
>
> there are a few errors in latest builds
> {noformat}
> Error fetching link: 
> /home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/sharelib/hcatalog/target/site/apidocs/package-list
> {noformat}
> that can be downgraded to warning with latest maven-javadoc-plugin as well as 
> other fixes to the plugin, currently used 2.10.3 was released in 2015, 2.10.4 
> has a few fixes on top of that and was released in 2016.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (OOZIE-2964) Add -Xdoclint:none to javadoc opts to avoid warnings

2017-11-07 Thread Andras Piros (JIRA)

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

Andras Piros commented on OOZIE-2964:
-

[~dbist13] thanks for the contribution!

However, I don't like the possibility of having no Doclint checks at all. 
Wouldn't be a subset like 
[*{{-Xdoclint:html,syntax,accessibility}}*|https://docs.oracle.com/javase/8/docs/technotes/tools/windows/javadoc.html#BEJEFABE]
 better? Even switching on for only {{public}} methods? All the relevant 
Doclint checks that still exists would be handled either here or in a follow-up 
JIRA.

> Add -Xdoclint:none to javadoc opts to avoid warnings
> 
>
> Key: OOZIE-2964
> URL: https://issues.apache.org/jira/browse/OOZIE-2964
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
> Environment: java version "1.8.0_51"
> Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
> Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
> Mac OSX 10.12.5
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2964-0.patch
>
>
> steps to reproduce
> {noformat}
> ./bin/mkdistro.sh -DskipTests=true -DtargetJavaVersion=1.8 -DjavaVersion=1.8
> {noformat}
> Refer to the generated Javadoc files in 
> '/Users/aervits/NetBeansProjects/OOZIE-AbstractJavadocMojo/oozie/core/target/site/apidocs'
>  dir.
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:5163)
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:2075)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:130)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:318)
> at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> 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:497)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (OOZIE-2996) add option for -UseGCOverheadLimit to maven opts as sometimes local testing fails

2017-11-07 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-2996:
--

Testing JIRA OOZIE-2996

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch



> add option for -UseGCOverheadLimit to maven opts as sometimes local testing 
> fails
> -
>
> Key: OOZIE-2996
> URL: https://issues.apache.org/jira/browse/OOZIE-2996
> Project: Oozie
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: 4.3.0
> Environment: Java 8
> Maven 3.5
> Oozie master branch commit 50b92932f54d46e342403acaa33b7ae1a524328c
>Reporter: Artem Ervits
>Assignee: Artem Ervits
> Fix For: 5.0.0
>
> Attachments: OOZIE-2996-0.patch
>
>
> steps to reproduce
> {code}
> mvn clean -Dtest=org.apache.oozie.service.TestAuthorizationService test 
> -DtargetJavaVersion=1.8 -DjavaVersion=1.8
> {code}
> {noformat}
> [INFO] Apache Oozie Main .. SUCCESS [  0.635 
> s]
> [INFO] Apache Oozie Client  SUCCESS [  3.648 
> s]
> [INFO] Apache Oozie Share Lib Oozie ... SUCCESS [  4.660 
> s]
> [INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  1.762 
> s]
> [INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  1.012 
> s]
> [INFO] Apache Oozie Core .. SUCCESS [02:28 
> min]
> [INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  4.101 
> s]
> [INFO] Apache Oozie Share Lib Pig . SUCCESS [  3.101 
> s]
> [INFO] Apache Oozie Share Lib Hive  SUCCESS [  3.129 
> s]
> [INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  4.354 
> s]
> [INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  3.280 
> s]
> [INFO] Apache Oozie Examples .. SUCCESS [  7.110 
> s]
> [INFO] Apache Oozie Share Lib Spark ... SUCCESS [  8.048 
> s]
> [INFO] Apache Oozie Share Lib . SUCCESS [  0.018 
> s]
> [INFO] Apache Oozie Docs .. SUCCESS [  0.284 
> s]
> [INFO] Apache Oozie WebApp  FAILURE [ 24.500 
> s]
> [INFO] Apache Oozie Tools . SKIPPED
> [INFO] Apache Oozie MiniOozie . SKIPPED
> [INFO] Apache Oozie Server  SKIPPED
> [INFO] Apache Oozie Distro  SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 03:39 min
> [INFO] Finished at: 2017-07-17T16:39:33-04:00
> [INFO] Final Memory: 239M/455M
> [INFO] 
> 
> [ERROR] GC overhead limit exceeded -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Failed: OOZIE-2996 PreCommit Build #182

2017-11-07 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/OOZIE-2996
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/182/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 678.30 KB...]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [ 10.756 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [ 11.222 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  7.501 s]
[INFO] Apache Oozie Examples .. SUCCESS [ 12.249 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 13.145 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.022 s]
[INFO] Apache Oozie Docs .. SUCCESS [  4.776 s]
[INFO] Apache Oozie WebApp  SUCCESS [  3.671 s]
[INFO] Apache Oozie Tools . SUCCESS [ 15.389 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  2.654 s]
[INFO] Apache Oozie Server  SUCCESS [ 13.869 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.389 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  4.207 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 04:27 min
[INFO] Finished at: 2017-11-07T09:11:46Z
[INFO] Final Memory: 642M/1921M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch pom.xml...
error: while searching for:
once


true
-Xmx1024m -da 
-XX:MaxPermSize=512m


${oozie.test.dir}

error: patch failed: pom.xml:68
error: pom.xml: patch does not apply
fatal: git diff header lacks filename information when removing 1 leading 
pathname component (line 5)
Patch failed to apply to head of branch

  % 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
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100 3706k  100 3706k0 0  4135k  0 --:--:-- --:--:-- --:--:-- 8639k
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-2996
Archiving artifacts
[Fast Archiver] Compressed 844.42 KB of artifacts by 37.9% relative to #164
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Commented] (OOZIE-2996) add option for -UseGCOverheadLimit to maven opts as sometimes local testing fails

2017-11-07 Thread Andras Piros (JIRA)

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

Andras Piros commented on OOZIE-2996:
-

[~dbist13] thanks for the contribution! Are you sure we can't get 
{{java.lang.OutOfMemoryError: Java heap space}} instead of {{GC overhead limit 
exceeded}}? Isn't setting of metaspace size (speaking of JDK8), and enabling 
parallel GC a better option?
{noformat}
-XX:MetaspaceSize=512M -XX:MaxMetaspaceSize=1024M -XX:+CMSClassUnloadingEnabled 
-XX:+UseConcMarkSweepGC
{noformat}

> add option for -UseGCOverheadLimit to maven opts as sometimes local testing 
> fails
> -
>
> Key: OOZIE-2996
> URL: https://issues.apache.org/jira/browse/OOZIE-2996
> Project: Oozie
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: 4.3.0
> Environment: Java 8
> Maven 3.5
> Oozie master branch commit 50b92932f54d46e342403acaa33b7ae1a524328c
>Reporter: Artem Ervits
>Assignee: Artem Ervits
> Fix For: 5.0.0
>
> Attachments: OOZIE-2996-0.patch
>
>
> steps to reproduce
> {code}
> mvn clean -Dtest=org.apache.oozie.service.TestAuthorizationService test 
> -DtargetJavaVersion=1.8 -DjavaVersion=1.8
> {code}
> {noformat}
> [INFO] Apache Oozie Main .. SUCCESS [  0.635 
> s]
> [INFO] Apache Oozie Client  SUCCESS [  3.648 
> s]
> [INFO] Apache Oozie Share Lib Oozie ... SUCCESS [  4.660 
> s]
> [INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  1.762 
> s]
> [INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  1.012 
> s]
> [INFO] Apache Oozie Core .. SUCCESS [02:28 
> min]
> [INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  4.101 
> s]
> [INFO] Apache Oozie Share Lib Pig . SUCCESS [  3.101 
> s]
> [INFO] Apache Oozie Share Lib Hive  SUCCESS [  3.129 
> s]
> [INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  4.354 
> s]
> [INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  3.280 
> s]
> [INFO] Apache Oozie Examples .. SUCCESS [  7.110 
> s]
> [INFO] Apache Oozie Share Lib Spark ... SUCCESS [  8.048 
> s]
> [INFO] Apache Oozie Share Lib . SUCCESS [  0.018 
> s]
> [INFO] Apache Oozie Docs .. SUCCESS [  0.284 
> s]
> [INFO] Apache Oozie WebApp  FAILURE [ 24.500 
> s]
> [INFO] Apache Oozie Tools . SKIPPED
> [INFO] Apache Oozie MiniOozie . SKIPPED
> [INFO] Apache Oozie Server  SKIPPED
> [INFO] Apache Oozie Distro  SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 03:39 min
> [INFO] Finished at: 2017-07-17T16:39:33-04:00
> [INFO] Final Memory: 239M/455M
> [INFO] 
> 
> [ERROR] GC overhead limit exceeded -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)