Build failed in Jenkins: oozie-trunk-precommit-build #2105

2014-11-24 Thread Apache Jenkins Server
See https://builds.apache.org/job/oozie-trunk-precommit-build/2105/

--
[...truncated 10806 lines...]
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-tools ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-tools ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-tools ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml
[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  '*:*:pom:*'

[INFO] Copying files to 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools
[WARNING] Assembly file: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools
 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.2.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/src/main/resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/target/oozie-mini-4.2.0-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.2.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/main/resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/test/resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/target/oozie-distro-4.2.0-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

main:
  [get] Getting: 
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.41/bin/apache-tomcat-6.0.41.tar.gz
  [get] To: 

[jira] [Commented] (OOZIE-2028) Coord action rerun with -failed option should rerun existing workflow with RERUN_FAIL_NODES=true

2014-11-24 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222796#comment-14222796
 ] 

Hadoop QA commented on OOZIE-2028:
--

Testing JIRA OOZIE-2028

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:red}-1{color} the patch contains 2 line(s) longer than 132 
characters
.{color:green}+1{color} the patch does adds/modifies 6 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1558
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/2105/

 Coord action rerun with -failed option should rerun existing workflow with 
 RERUN_FAIL_NODES=true
 

 Key: OOZIE-2028
 URL: https://issues.apache.org/jira/browse/OOZIE-2028
 Project: Oozie
  Issue Type: Sub-task
  Components: workflow
Affects Versions: trunk
Reporter: Jaydeep Vishwakarma
Assignee: Jaydeep Vishwakarma
 Attachments: OOZIE-2028-v0.patch, OOZIE-2028-v1.patch


 1. Coord action re-run will take an addition optional flag -failed which 
 re-run only the failed nodes. This will re-run the existing workflow with 
 RERUN_FAIL_NODES=true. But this will also honour coord concurrency.
 2. Coord action re-run with no -failed option will use the existing feature 
 of launching new workflow.



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


[jira] [Created] (OOZIE-2074) Compatibility issue with Yarn and Hadoop 0.23/2.x

2014-11-24 Thread Jaydeep Vishwakarma (JIRA)
Jaydeep Vishwakarma created OOZIE-2074:
--

 Summary: Compatibility issue with Yarn and Hadoop 0.23/2.x
 Key: OOZIE-2074
 URL: https://issues.apache.org/jira/browse/OOZIE-2074
 Project: Oozie
  Issue Type: Bug
Reporter: Jaydeep Vishwakarma
Assignee: Jaydeep Vishwakarma


We are using yarn.resourcemanager.address for checking the hadoop version in 
jobUtils. Here is the code snippet. 
 // Hadoop 0.20/1.x.
  if (defaultConf.get(yarn.resourcemanager.address) == null) {
  // Duplicate hadoop 1.x code to workaround MAPREDUCE-2361 in Hadoop 
0.20
  // Refer OOZIE-1806.
  String filepath = file.toUri().getPath();
  String classpath = conf.get(mapred.job.classpath.files);
  conf.set(mapred.job.classpath.files, classpath == null
  ? filepath
  : classpath + System.getProperty(path.separator) + filepath);
  URI uri = fs.makeQualified(file).toUri();
  DistributedCache.addCacheFile(uri, conf);
  }
  else { // Hadoop 0.23/2.x
  DistributedCache.addFileToClassPath(file, conf, fs);
  }

But this is being used in JavaActionExecutor to set jobTracker.
conf.set(HADOOP_YARN_RM, jobTracker);





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


[jira] [Assigned] (OOZIE-2071) Add a Spark example

2014-11-24 Thread pavan kumar kolamuri (JIRA)

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

pavan kumar kolamuri reassigned OOZIE-2071:
---

Assignee: pavan kumar kolamuri

 Add a Spark example
 ---

 Key: OOZIE-2071
 URL: https://issues.apache.org/jira/browse/OOZIE-2071
 Project: Oozie
  Issue Type: Sub-task
  Components: examples
Affects Versions: trunk
Reporter: Robert Kanter
Assignee: pavan kumar kolamuri
 Fix For: trunk


 With the new Spark action, we should have a Spark example workflow that runs 
 some Spark job.



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


[jira] [Commented] (OOZIE-1983) Add spark action executor

2014-11-24 Thread pavan kumar kolamuri (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222940#comment-14222940
 ] 

pavan kumar kolamuri commented on OOZIE-1983:
-

[~shwethags] [~rkanter]  Thanks for reviewing patch and for suggestions. I 
don't see any javac warnings from my patch . Can you guys please merge it.  
[~rkanter]  I will take up this 
https://issues.apache.org/jira/browse/OOZIE-2071 (Add spark example)

 Add spark action executor
 -

 Key: OOZIE-1983
 URL: https://issues.apache.org/jira/browse/OOZIE-1983
 Project: Oozie
  Issue Type: New Feature
Reporter: Shwetha G S
Assignee: pavan kumar kolamuri
  Labels: spark
 Fix For: trunk

 Attachments: OOZIE-1983v2.patch, OOZIE-1983v3.patch, 
 OOZIE-1983v4.patch, spark-actionv1.patch






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


[jira] [Commented] (OOZIE-2074) Compatibility issue with Yarn and Hadoop 0.23/2.x

2014-11-24 Thread Jaydeep Vishwakarma (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222941#comment-14222941
 ] 

Jaydeep Vishwakarma commented on OOZIE-2074:


Checking the yarn.resourcemanager.webapp.address property will be fine 
instead of yarn.resourcemanager.address.

 Compatibility issue with Yarn and Hadoop 0.23/2.x
 -

 Key: OOZIE-2074
 URL: https://issues.apache.org/jira/browse/OOZIE-2074
 Project: Oozie
  Issue Type: Bug
Reporter: Jaydeep Vishwakarma
Assignee: Jaydeep Vishwakarma

 We are using yarn.resourcemanager.address for checking the hadoop version 
 in jobUtils. Here is the code snippet. 
  // Hadoop 0.20/1.x.
   if (defaultConf.get(yarn.resourcemanager.address) == null) {
   // Duplicate hadoop 1.x code to workaround MAPREDUCE-2361 in Hadoop 
 0.20
   // Refer OOZIE-1806.
   String filepath = file.toUri().getPath();
   String classpath = conf.get(mapred.job.classpath.files);
   conf.set(mapred.job.classpath.files, classpath == null
   ? filepath
   : classpath + System.getProperty(path.separator) + filepath);
   URI uri = fs.makeQualified(file).toUri();
   DistributedCache.addCacheFile(uri, conf);
   }
   else { // Hadoop 0.23/2.x
   DistributedCache.addFileToClassPath(file, conf, fs);
   }
 But this is being used in JavaActionExecutor to set jobTracker.
 conf.set(HADOOP_YARN_RM, jobTracker);



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


[jira] [Updated] (OOZIE-2074) Compatibility issue with Yarn and Hadoop 0.23/2.x

2014-11-24 Thread Jaydeep Vishwakarma (JIRA)

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

Jaydeep Vishwakarma updated OOZIE-2074:
---
Attachment: OOZIE-2074-v0.patch

 Compatibility issue with Yarn and Hadoop 0.23/2.x
 -

 Key: OOZIE-2074
 URL: https://issues.apache.org/jira/browse/OOZIE-2074
 Project: Oozie
  Issue Type: Bug
Reporter: Jaydeep Vishwakarma
Assignee: Jaydeep Vishwakarma
 Attachments: OOZIE-2074-v0.patch


 We are using yarn.resourcemanager.address for checking the hadoop version 
 in jobUtils. Here is the code snippet. 
  // Hadoop 0.20/1.x.
   if (defaultConf.get(yarn.resourcemanager.address) == null) {
   // Duplicate hadoop 1.x code to workaround MAPREDUCE-2361 in Hadoop 
 0.20
   // Refer OOZIE-1806.
   String filepath = file.toUri().getPath();
   String classpath = conf.get(mapred.job.classpath.files);
   conf.set(mapred.job.classpath.files, classpath == null
   ? filepath
   : classpath + System.getProperty(path.separator) + filepath);
   URI uri = fs.makeQualified(file).toUri();
   DistributedCache.addCacheFile(uri, conf);
   }
   else { // Hadoop 0.23/2.x
   DistributedCache.addFileToClassPath(file, conf, fs);
   }
 But this is being used in JavaActionExecutor to set jobTracker.
 conf.set(HADOOP_YARN_RM, jobTracker);



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


[jira] [Updated] (OOZIE-2074) Compatibility issue with Yarn and Hadoop 0.23/2.x

2014-11-24 Thread Jaydeep Vishwakarma (JIRA)

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

Jaydeep Vishwakarma updated OOZIE-2074:
---
Description: 
We are using yarn.resourcemanager.address for checking the hadoop version in 
jobUtils. Here is the code snippet. 
 // Hadoop 0.20/1.x.
{code}
  if (defaultConf.get(yarn.resourcemanager.address) == null) {
  // Duplicate hadoop 1.x code to workaround MAPREDUCE-2361 in Hadoop 
0.20
  // Refer OOZIE-1806.
  String filepath = file.toUri().getPath();
  String classpath = conf.get(mapred.job.classpath.files);
  conf.set(mapred.job.classpath.files, classpath == null
  ? filepath
  : classpath + System.getProperty(path.separator) + filepath);
  URI uri = fs.makeQualified(file).toUri();
  DistributedCache.addCacheFile(uri, conf);
  }
  else { // Hadoop 0.23/2.x
  DistributedCache.addFileToClassPath(file, conf, fs);
  }
{code}
But this is being used in JavaActionExecutor to set jobTracker.
conf.set(HADOOP_YARN_RM, jobTracker);



  was:
We are using yarn.resourcemanager.address for checking the hadoop version in 
jobUtils. Here is the code snippet. 
 // Hadoop 0.20/1.x.
  if (defaultConf.get(yarn.resourcemanager.address) == null) {
  // Duplicate hadoop 1.x code to workaround MAPREDUCE-2361 in Hadoop 
0.20
  // Refer OOZIE-1806.
  String filepath = file.toUri().getPath();
  String classpath = conf.get(mapred.job.classpath.files);
  conf.set(mapred.job.classpath.files, classpath == null
  ? filepath
  : classpath + System.getProperty(path.separator) + filepath);
  URI uri = fs.makeQualified(file).toUri();
  DistributedCache.addCacheFile(uri, conf);
  }
  else { // Hadoop 0.23/2.x
  DistributedCache.addFileToClassPath(file, conf, fs);
  }

But this is being used in JavaActionExecutor to set jobTracker.
conf.set(HADOOP_YARN_RM, jobTracker);




 Compatibility issue with Yarn and Hadoop 0.23/2.x
 -

 Key: OOZIE-2074
 URL: https://issues.apache.org/jira/browse/OOZIE-2074
 Project: Oozie
  Issue Type: Bug
Reporter: Jaydeep Vishwakarma
Assignee: Jaydeep Vishwakarma
 Attachments: OOZIE-2074-v0.patch


 We are using yarn.resourcemanager.address for checking the hadoop version 
 in jobUtils. Here is the code snippet. 
  // Hadoop 0.20/1.x.
 {code}
   if (defaultConf.get(yarn.resourcemanager.address) == null) {
   // Duplicate hadoop 1.x code to workaround MAPREDUCE-2361 in Hadoop 
 0.20
   // Refer OOZIE-1806.
   String filepath = file.toUri().getPath();
   String classpath = conf.get(mapred.job.classpath.files);
   conf.set(mapred.job.classpath.files, classpath == null
   ? filepath
   : classpath + System.getProperty(path.separator) + filepath);
   URI uri = fs.makeQualified(file).toUri();
   DistributedCache.addCacheFile(uri, conf);
   }
   else { // Hadoop 0.23/2.x
   DistributedCache.addFileToClassPath(file, conf, fs);
   }
 {code}
 But this is being used in JavaActionExecutor to set jobTracker.
 conf.set(HADOOP_YARN_RM, jobTracker);



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


[jira] [Commented] (OOZIE-2074) Compatibility issue with Yarn and Hadoop 0.23/2.x

2014-11-24 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223018#comment-14223018
 ] 

Hadoop QA commented on OOZIE-2074:
--

Testing JIRA OOZIE-2074

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: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 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1557
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/2106/

 Compatibility issue with Yarn and Hadoop 0.23/2.x
 -

 Key: OOZIE-2074
 URL: https://issues.apache.org/jira/browse/OOZIE-2074
 Project: Oozie
  Issue Type: Bug
Reporter: Jaydeep Vishwakarma
Assignee: Jaydeep Vishwakarma
 Attachments: OOZIE-2074-v0.patch


 We are using yarn.resourcemanager.address for checking the hadoop version 
 in jobUtils. Here is the code snippet. 
  // Hadoop 0.20/1.x.
 {code}
   if (defaultConf.get(yarn.resourcemanager.address) == null) {
   // Duplicate hadoop 1.x code to workaround MAPREDUCE-2361 in Hadoop 
 0.20
   // Refer OOZIE-1806.
   String filepath = file.toUri().getPath();
   String classpath = conf.get(mapred.job.classpath.files);
   conf.set(mapred.job.classpath.files, classpath == null
   ? filepath
   : classpath + System.getProperty(path.separator) + filepath);
   URI uri = fs.makeQualified(file).toUri();
   DistributedCache.addCacheFile(uri, conf);
   }
   else { // Hadoop 0.23/2.x
   DistributedCache.addFileToClassPath(file, conf, fs);
   }
 {code}
 But this is being used in JavaActionExecutor to set jobTracker.
 conf.set(HADOOP_YARN_RM, jobTracker);



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


Build failed in Jenkins: oozie-trunk-precommit-build #2106

2014-11-24 Thread Apache Jenkins Server
See https://builds.apache.org/job/oozie-trunk-precommit-build/2106/

--
[...truncated 16892 lines...]
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml
[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  '*:*:pom:*'

[INFO] Copying files to 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools
[WARNING] Assembly file: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools
 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.2.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/src/main/resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/target/oozie-mini-4.2.0-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.2.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/main/resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/test/resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/target/oozie-distro-4.2.0-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

main:
[mkdir] Created dir: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/downloads
  [get] Getting: 
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.41/bin/apache-tomcat-6.0.41.tar.gz
  [get] To: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/downloads/tomcat-6.0.41.tar.gz

[jira] Subscription: Oozie Patch Available

2014-11-24 Thread jira
Issue Subscription
Filter: Oozie Patch Available (46 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2074  Compatibility issue with Yarn and Hadoop 0.23/2.x
https://issues.apache.org/jira/browse/OOZIE-2074
OOZIE-2072  Improve the whitelist error message by showing allowed values
https://issues.apache.org/jira/browse/OOZIE-2072
OOZIE-2069  RecoveryService reads incorrect configuration 
https://issues.apache.org/jira/browse/OOZIE-2069
OOZIE-2065  Oozie returns incorrect total action for coord dryrun
https://issues.apache.org/jira/browse/OOZIE-2065
OOZIE-2060  Incorrect documentation of Java action config XML filename
https://issues.apache.org/jira/browse/OOZIE-2060
OOZIE-2055  PauseTransitService does not proceed forward if any job has issue 
https://issues.apache.org/jira/browse/OOZIE-2055
OOZIE-2051  Allows multiple default action configuration files per action
https://issues.apache.org/jira/browse/OOZIE-2051
OOZIE-2044  ssh action succeed with a not exists command which should be fail.
https://issues.apache.org/jira/browse/OOZIE-2044
OOZIE-2035  NotificationXCommand should support proxy
https://issues.apache.org/jira/browse/OOZIE-2035
OOZIE-2029  Workflow re-run with RERUN_FAIL_NODES=true should re-run only the 
failed nodes of the sub-workflow
https://issues.apache.org/jira/browse/OOZIE-2029
OOZIE-2028  Coord action rerun with -failed option should rerun existing 
workflow with RERUN_FAIL_NODES=true
https://issues.apache.org/jira/browse/OOZIE-2028
OOZIE-2024  Confusing message when a job can't be looked up by 
JavaActionExecutor
https://issues.apache.org/jira/browse/OOZIE-2024
OOZIE-1980  Sql error should not fail coord job
https://issues.apache.org/jira/browse/OOZIE-1980
OOZIE-1977  Display patch analysis issues
https://issues.apache.org/jira/browse/OOZIE-1977
OOZIE-1936  Queuedump command should display queue information for all server.
https://issues.apache.org/jira/browse/OOZIE-1936
OOZIE-1931  Admin command to print all locks held by server(s)
https://issues.apache.org/jira/browse/OOZIE-1931
OOZIE-1927  Use StoreStatusFilter for WorkflowsJobGetJPAExecutor 
https://issues.apache.org/jira/browse/OOZIE-1927
OOZIE-1922  MemoryLocksService fails if lock is acquired multiple times in same 
thread and released
https://issues.apache.org/jira/browse/OOZIE-1922
OOZIE-1918  ActionXCommand refactoring for code reuse
https://issues.apache.org/jira/browse/OOZIE-1918
OOZIE-1889  Convert NamedNativeQueries to JPQL
https://issues.apache.org/jira/browse/OOZIE-1889
OOZIE-1884  ZKJobsConcurrencyService.checkJobIdForServer fails if jobs length  
7
https://issues.apache.org/jira/browse/OOZIE-1884
OOZIE-1876  use pom properties rather than specific version numbers in the pom 
files of hbaselibs, hcataloglibs, sharelib, etc 
https://issues.apache.org/jira/browse/OOZIE-1876
OOZIE-1860  Oozie job mapper launch fails due to null value returned from 
action file
https://issues.apache.org/jira/browse/OOZIE-1860
OOZIE-1855  TestPriorityDelayQueue#testPoll failed intermittently in Jenkins
https://issues.apache.org/jira/browse/OOZIE-1855
OOZIE-1829  URIHandlerService doesn't support URI schemes with query strings 
but no path segment
https://issues.apache.org/jira/browse/OOZIE-1829
OOZIE-1816  LogInfo uses action name instead of id
https://issues.apache.org/jira/browse/OOZIE-1816
OOZIE-1810  Workflow cannot get into Failed state when kill control node cannot 
resolve variable in message 
https://issues.apache.org/jira/browse/OOZIE-1810
OOZIE-1802  Support workflow action log
https://issues.apache.org/jira/browse/OOZIE-1802
OOZIE-1793  Improve find bugs reporting for Oozie
https://issues.apache.org/jira/browse/OOZIE-1793
OOZIE-1782  Workflow path not found is thrown as SC_UNAUTHORIZED
https://issues.apache.org/jira/browse/OOZIE-1782
OOZIE-1779  Add parent-id as a filter option
https://issues.apache.org/jira/browse/OOZIE-1779
OOZIE-1705  Enable gc logs and print thread id in logs
https://issues.apache.org/jira/browse/OOZIE-1705
OOZIE-1688  New configuration to specify server-server authentication type.
https://issues.apache.org/jira/browse/OOZIE-1688
OOZIE-1676  Instrumentation and Configuration over the REST API and Web UI 
should include all Oozie servers
https://issues.apache.org/jira/browse/OOZIE-1676
OOZIE-1654  Fix typo (inteval to interval)
https://issues.apache.org/jira/browse/OOZIE-1654
OOZIE-1638  Action retry does not use default retry max count.
https://issues.apache.org/jira/browse/OOZIE-1638
OOZIE-1636  OOZIE_SYS table engine should be innodb