[jira] [Commented] (YARN-129) Simplify classpath construction for mini YARN tests

2013-05-14 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13657616#comment-13657616
 ] 

Hudson commented on YARN-129:
-

Integrated in HBase-TRUNK #4117 (See 
[https://builds.apache.org/job/HBase-TRUNK/4117/])
HBASE-8528 [hadoop2] TestMultiTableInputFormat always hadoop with YARN-129 
applied (with Gary Helmling) (Revision 1482561)

 Result = FAILURE
jmhsieh : 
Files : 
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java


 Simplify classpath construction for mini YARN tests
 ---

 Key: YARN-129
 URL: https://issues.apache.org/jira/browse/YARN-129
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: client
Reporter: Tom White
Assignee: Tom White
 Fix For: 2.0.3-alpha

 Attachments: YARN-129.patch, YARN-129.patch, YARN-129.patch


 The test classpath includes a special file called 'mrapp-generated-classpath' 
 (or similar in distributed shell) that is constructed at build time, and 
 whose contents are a classpath with all the dependencies needed to run the 
 tests. When the classpath for a container (e.g. the AM) is constructed the 
 contents of mrapp-generated-classpath is read and added to the classpath, and 
 the file itself is then added to the classpath so that later when the AM 
 constructs a classpath for a task container it can propagate the test 
 classpath correctly.
 This mechanism can be drastically simplified by propagating the system 
 classpath of the current JVM (read from the java.class.path property) to a 
 launched JVM, but only if running in the context of the mini YARN cluster. 
 Any tests that use the mini YARN cluster will automatically work with this 
 change. Although any that explicitly deal with mrapp-generated-classpath can 
 be simplified.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-129) Simplify classpath construction for mini YARN tests

2013-05-14 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13657767#comment-13657767
 ] 

Hudson commented on YARN-129:
-

Integrated in hbase-0.95 #193 (See 
[https://builds.apache.org/job/hbase-0.95/193/])
HBASE-8528 [hadoop2] TestMultiTableInputFormat always on hadoop with 
YARN-129 applied (with Gary Helmling) (Revision 1482563)

 Result = SUCCESS
jmhsieh : 
Files : 
* 
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java


 Simplify classpath construction for mini YARN tests
 ---

 Key: YARN-129
 URL: https://issues.apache.org/jira/browse/YARN-129
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: client
Reporter: Tom White
Assignee: Tom White
 Fix For: 2.0.3-alpha

 Attachments: YARN-129.patch, YARN-129.patch, YARN-129.patch


 The test classpath includes a special file called 'mrapp-generated-classpath' 
 (or similar in distributed shell) that is constructed at build time, and 
 whose contents are a classpath with all the dependencies needed to run the 
 tests. When the classpath for a container (e.g. the AM) is constructed the 
 contents of mrapp-generated-classpath is read and added to the classpath, and 
 the file itself is then added to the classpath so that later when the AM 
 constructs a classpath for a task container it can propagate the test 
 classpath correctly.
 This mechanism can be drastically simplified by propagating the system 
 classpath of the current JVM (read from the java.class.path property) to a 
 launched JVM, but only if running in the context of the mini YARN cluster. 
 Any tests that use the mini YARN cluster will automatically work with this 
 change. Although any that explicitly deal with mrapp-generated-classpath can 
 be simplified.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-129) Simplify classpath construction for mini YARN tests

2013-05-14 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13657857#comment-13657857
 ] 

Hudson commented on YARN-129:
-

Integrated in hbase-0.95-on-hadoop2 #99 (See 
[https://builds.apache.org/job/hbase-0.95-on-hadoop2/99/])
HBASE-8528 [hadoop2] TestMultiTableInputFormat always on hadoop with 
YARN-129 applied (with Gary Helmling) (Revision 1482563)

 Result = FAILURE
jmhsieh : 
Files : 
* 
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java


 Simplify classpath construction for mini YARN tests
 ---

 Key: YARN-129
 URL: https://issues.apache.org/jira/browse/YARN-129
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: client
Reporter: Tom White
Assignee: Tom White
 Fix For: 2.0.3-alpha

 Attachments: YARN-129.patch, YARN-129.patch, YARN-129.patch


 The test classpath includes a special file called 'mrapp-generated-classpath' 
 (or similar in distributed shell) that is constructed at build time, and 
 whose contents are a classpath with all the dependencies needed to run the 
 tests. When the classpath for a container (e.g. the AM) is constructed the 
 contents of mrapp-generated-classpath is read and added to the classpath, and 
 the file itself is then added to the classpath so that later when the AM 
 constructs a classpath for a task container it can propagate the test 
 classpath correctly.
 This mechanism can be drastically simplified by propagating the system 
 classpath of the current JVM (read from the java.class.path property) to a 
 launched JVM, but only if running in the context of the mini YARN cluster. 
 Any tests that use the mini YARN cluster will automatically work with this 
 change. Although any that explicitly deal with mrapp-generated-classpath can 
 be simplified.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-129) Simplify classpath construction for mini YARN tests

2013-05-14 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13657876#comment-13657876
 ] 

Hudson commented on YARN-129:
-

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #530 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/530/])
HBASE-8528 [hadoop2] TestMultiTableInputFormat always hadoop with YARN-129 
applied (with Gary Helmling) (Revision 1482561)

 Result = FAILURE
jmhsieh : 
Files : 
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java


 Simplify classpath construction for mini YARN tests
 ---

 Key: YARN-129
 URL: https://issues.apache.org/jira/browse/YARN-129
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: client
Reporter: Tom White
Assignee: Tom White
 Fix For: 2.0.3-alpha

 Attachments: YARN-129.patch, YARN-129.patch, YARN-129.patch


 The test classpath includes a special file called 'mrapp-generated-classpath' 
 (or similar in distributed shell) that is constructed at build time, and 
 whose contents are a classpath with all the dependencies needed to run the 
 tests. When the classpath for a container (e.g. the AM) is constructed the 
 contents of mrapp-generated-classpath is read and added to the classpath, and 
 the file itself is then added to the classpath so that later when the AM 
 constructs a classpath for a task container it can propagate the test 
 classpath correctly.
 This mechanism can be drastically simplified by propagating the system 
 classpath of the current JVM (read from the java.class.path property) to a 
 launched JVM, but only if running in the context of the mini YARN cluster. 
 Any tests that use the mini YARN cluster will automatically work with this 
 change. Although any that explicitly deal with mrapp-generated-classpath can 
 be simplified.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-129) Simplify classpath construction for mini YARN tests

2012-11-20 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500991#comment-13500991
 ] 

Hudson commented on YARN-129:
-

Integrated in Hadoop-Yarn-trunk #42 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/42/])
YARN-129. Simplify classpath construction for mini YARN tests. (Revision 
1411235)

 Result = SUCCESS
tomwhite : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1411235
Files : 
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/pom.xml
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/util/MRApps.java
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/security/ssl/TestEncryptedShuffle.java
* /hadoop/common/trunk/hadoop-project/pom.xml
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/pom.xml
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/src/main/java/org/apache/hadoop/yarn/applications/distributedshell/Client.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher/pom.xml
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher/src/test/java/org/apache/hadoop/yarn/applications/unmanagedamlauncher/TestUnmanagedAMLauncher.java


 Simplify classpath construction for mini YARN tests
 ---

 Key: YARN-129
 URL: https://issues.apache.org/jira/browse/YARN-129
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: client
Reporter: Tom White
Assignee: Tom White
 Fix For: 2.0.3-alpha

 Attachments: YARN-129.patch, YARN-129.patch, YARN-129.patch


 The test classpath includes a special file called 'mrapp-generated-classpath' 
 (or similar in distributed shell) that is constructed at build time, and 
 whose contents are a classpath with all the dependencies needed to run the 
 tests. When the classpath for a container (e.g. the AM) is constructed the 
 contents of mrapp-generated-classpath is read and added to the classpath, and 
 the file itself is then added to the classpath so that later when the AM 
 constructs a classpath for a task container it can propagate the test 
 classpath correctly.
 This mechanism can be drastically simplified by propagating the system 
 classpath of the current JVM (read from the java.class.path property) to a 
 launched JVM, but only if running in the context of the mini YARN cluster. 
 Any tests that use the mini YARN cluster will automatically work with this 
 change. Although any that explicitly deal with mrapp-generated-classpath can 
 be simplified.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-129) Simplify classpath construction for mini YARN tests

2012-11-20 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501160#comment-13501160
 ] 

Hudson commented on YARN-129:
-

Integrated in Hadoop-Hdfs-trunk #1232 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1232/])
YARN-129. Simplify classpath construction for mini YARN tests. (Revision 
1411235)

 Result = SUCCESS
tomwhite : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1411235
Files : 
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/pom.xml
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/util/MRApps.java
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/security/ssl/TestEncryptedShuffle.java
* /hadoop/common/trunk/hadoop-project/pom.xml
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/pom.xml
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/src/main/java/org/apache/hadoop/yarn/applications/distributedshell/Client.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher/pom.xml
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher/src/test/java/org/apache/hadoop/yarn/applications/unmanagedamlauncher/TestUnmanagedAMLauncher.java


 Simplify classpath construction for mini YARN tests
 ---

 Key: YARN-129
 URL: https://issues.apache.org/jira/browse/YARN-129
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: client
Reporter: Tom White
Assignee: Tom White
 Fix For: 2.0.3-alpha

 Attachments: YARN-129.patch, YARN-129.patch, YARN-129.patch


 The test classpath includes a special file called 'mrapp-generated-classpath' 
 (or similar in distributed shell) that is constructed at build time, and 
 whose contents are a classpath with all the dependencies needed to run the 
 tests. When the classpath for a container (e.g. the AM) is constructed the 
 contents of mrapp-generated-classpath is read and added to the classpath, and 
 the file itself is then added to the classpath so that later when the AM 
 constructs a classpath for a task container it can propagate the test 
 classpath correctly.
 This mechanism can be drastically simplified by propagating the system 
 classpath of the current JVM (read from the java.class.path property) to a 
 launched JVM, but only if running in the context of the mini YARN cluster. 
 Any tests that use the mini YARN cluster will automatically work with this 
 change. Although any that explicitly deal with mrapp-generated-classpath can 
 be simplified.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-129) Simplify classpath construction for mini YARN tests

2012-11-20 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501179#comment-13501179
 ] 

Hudson commented on YARN-129:
-

Integrated in Hadoop-Mapreduce-trunk #1263 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1263/])
YARN-129. Simplify classpath construction for mini YARN tests. (Revision 
1411235)

 Result = FAILURE
tomwhite : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1411235
Files : 
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/pom.xml
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/util/MRApps.java
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/security/ssl/TestEncryptedShuffle.java
* /hadoop/common/trunk/hadoop-project/pom.xml
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/pom.xml
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/src/main/java/org/apache/hadoop/yarn/applications/distributedshell/Client.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher/pom.xml
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher/src/test/java/org/apache/hadoop/yarn/applications/unmanagedamlauncher/TestUnmanagedAMLauncher.java


 Simplify classpath construction for mini YARN tests
 ---

 Key: YARN-129
 URL: https://issues.apache.org/jira/browse/YARN-129
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: client
Reporter: Tom White
Assignee: Tom White
 Fix For: 2.0.3-alpha

 Attachments: YARN-129.patch, YARN-129.patch, YARN-129.patch


 The test classpath includes a special file called 'mrapp-generated-classpath' 
 (or similar in distributed shell) that is constructed at build time, and 
 whose contents are a classpath with all the dependencies needed to run the 
 tests. When the classpath for a container (e.g. the AM) is constructed the 
 contents of mrapp-generated-classpath is read and added to the classpath, and 
 the file itself is then added to the classpath so that later when the AM 
 constructs a classpath for a task container it can propagate the test 
 classpath correctly.
 This mechanism can be drastically simplified by propagating the system 
 classpath of the current JVM (read from the java.class.path property) to a 
 launched JVM, but only if running in the context of the mini YARN cluster. 
 Any tests that use the mini YARN cluster will automatically work with this 
 change. Although any that explicitly deal with mrapp-generated-classpath can 
 be simplified.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-129) Simplify classpath construction for mini YARN tests

2012-11-14 Thread Alejandro Abdelnur (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13497216#comment-13497216
 ] 

Alejandro Abdelnur commented on YARN-129:
-

+1

 Simplify classpath construction for mini YARN tests
 ---

 Key: YARN-129
 URL: https://issues.apache.org/jira/browse/YARN-129
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: client
Reporter: Tom White
Assignee: Tom White
 Attachments: YARN-129.patch, YARN-129.patch, YARN-129.patch


 The test classpath includes a special file called 'mrapp-generated-classpath' 
 (or similar in distributed shell) that is constructed at build time, and 
 whose contents are a classpath with all the dependencies needed to run the 
 tests. When the classpath for a container (e.g. the AM) is constructed the 
 contents of mrapp-generated-classpath is read and added to the classpath, and 
 the file itself is then added to the classpath so that later when the AM 
 constructs a classpath for a task container it can propagate the test 
 classpath correctly.
 This mechanism can be drastically simplified by propagating the system 
 classpath of the current JVM (read from the java.class.path property) to a 
 launched JVM, but only if running in the context of the mini YARN cluster. 
 Any tests that use the mini YARN cluster will automatically work with this 
 change. Although any that explicitly deal with mrapp-generated-classpath can 
 be simplified.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-129) Simplify classpath construction for mini YARN tests

2012-11-07 Thread Tom White (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13492416#comment-13492416
 ] 

Tom White commented on YARN-129:


The test failure is unrelated - see MAPREDUCE-4774.

bq. Tom, does this work when running tests from Maven? Asking because, if I 
recall correctly, Maven heavily uses classloaders and if they are used for the 
project classpath most likely the JVM java.class.path wont have the project 
classpath.

Yes it does. I checked and the JVM java.class.path is being set correctly by 
the Maven test runner.

 Simplify classpath construction for mini YARN tests
 ---

 Key: YARN-129
 URL: https://issues.apache.org/jira/browse/YARN-129
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: client
Reporter: Tom White
Assignee: Tom White
 Attachments: YARN-129.patch, YARN-129.patch, YARN-129.patch


 The test classpath includes a special file called 'mrapp-generated-classpath' 
 (or similar in distributed shell) that is constructed at build time, and 
 whose contents are a classpath with all the dependencies needed to run the 
 tests. When the classpath for a container (e.g. the AM) is constructed the 
 contents of mrapp-generated-classpath is read and added to the classpath, and 
 the file itself is then added to the classpath so that later when the AM 
 constructs a classpath for a task container it can propagate the test 
 classpath correctly.
 This mechanism can be drastically simplified by propagating the system 
 classpath of the current JVM (read from the java.class.path property) to a 
 launched JVM, but only if running in the context of the mini YARN cluster. 
 Any tests that use the mini YARN cluster will automatically work with this 
 change. Although any that explicitly deal with mrapp-generated-classpath can 
 be simplified.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-129) Simplify classpath construction for mini YARN tests

2012-10-24 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13483874#comment-13483874
 ] 

Hadoop QA commented on YARN-129:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12550482/YARN-129.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell
 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher:

  org.apache.hadoop.mapred.TestClusterMRNotification

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/124//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/124//console

This message is automatically generated.

 Simplify classpath construction for mini YARN tests
 ---

 Key: YARN-129
 URL: https://issues.apache.org/jira/browse/YARN-129
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: client
Reporter: Tom White
Assignee: Tom White
 Attachments: YARN-129.patch, YARN-129.patch, YARN-129.patch


 The test classpath includes a special file called 'mrapp-generated-classpath' 
 (or similar in distributed shell) that is constructed at build time, and 
 whose contents are a classpath with all the dependencies needed to run the 
 tests. When the classpath for a container (e.g. the AM) is constructed the 
 contents of mrapp-generated-classpath is read and added to the classpath, and 
 the file itself is then added to the classpath so that later when the AM 
 constructs a classpath for a task container it can propagate the test 
 classpath correctly.
 This mechanism can be drastically simplified by propagating the system 
 classpath of the current JVM (read from the java.class.path property) to a 
 launched JVM, but only if running in the context of the mini YARN cluster. 
 Any tests that use the mini YARN cluster will automatically work with this 
 change. Although any that explicitly deal with mrapp-generated-classpath can 
 be simplified.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-129) Simplify classpath construction for mini YARN tests

2012-09-25 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13462683#comment-13462683
 ] 

Hadoop QA commented on YARN-129:


-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12546493/YARN-129.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 2 new or modified test 
files.

+1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

+1 javadoc.  The javadoc tool did not generate any warning messages.

+1 eclipse:eclipse.  The patch built with eclipse:eclipse.

-1 findbugs.  The patch appears to introduce 2 new Findbugs (version 1.3.9) 
warnings.

+1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

+1 core tests.  The patch passed unit tests in 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell
 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher.

+1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-YARN-Build/51//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/51//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-common.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/51//console

This message is automatically generated.

 Simplify classpath construction for mini YARN tests
 ---

 Key: YARN-129
 URL: https://issues.apache.org/jira/browse/YARN-129
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: client
Reporter: Tom White
Assignee: Tom White
 Fix For: 2.0.3-alpha

 Attachments: YARN-129.patch


 The test classpath includes a special file called 'mrapp-generated-classpath' 
 (or similar in distributed shell) that is constructed at build time, and 
 whose contents are a classpath with all the dependencies needed to run the 
 tests. When the classpath for a container (e.g. the AM) is constructed the 
 contents of mrapp-generated-classpath is read and added to the classpath, and 
 the file itself is then added to the classpath so that later when the AM 
 constructs a classpath for a task container it can propagate the test 
 classpath correctly.
 This mechanism can be drastically simplified by propagating the system 
 classpath of the current JVM (read from the java.class.path property) to a 
 launched JVM, but only if running in the context of the mini YARN cluster. 
 Any tests that use the mini YARN cluster will automatically work with this 
 change. Although any that explicitly deal with mrapp-generated-classpath can 
 be simplified.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira