Build failed in Jenkins: Hadoop-Common-0.23-Build #419

2012-11-01 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Common-0.23-Build/419/changes

Changes:

[vinodkv] YARN-189. Fixed a deadlock between RM's ApplicationMasterService and 
the dispatcher. Contributed by Thomas Graves.
svn merge --ignore-ancestry -c 1404431 ../../trunk/

[bobby] svn merge -c 1404305 FIXES: MAPREDUCE-4724. job history web ui 
applications page should be sorted to display last app first (tgraves via bobby)

[bobby] svn merge -c 1404247 FIXES: YARN-166. capacity scheduler doesn't allow 
capacity  1.0 (tgraves via bobby)

[bobby] svn merge -c 1404228 FIXES: YARN-159. RM web ui applications page 
should be sorted to display last app first (tgraves via bobby)

[bobby] YARN-165. RM should point tracking URL to RM web page for app when AM 
fails Contributed by Jason Lowe.

[tgraves] MAPREDUCE-4752. Reduce MR AM memory usage through String Interning 
(Robert Evans via tgraves)

--
[...truncated 12493 lines...]

[INFO] 
[INFO] --- maven-clover2-plugin:3.0.5:clover (clover) @ hadoop-auth ---
[INFO] Using /default-clover-report descriptor.
[INFO] Using Clover report descriptor: /tmp/mvn800061237296264416resource
[INFO] Clover Version 3.0.2, built on April 13 2010 (build-790)
[INFO] Loaded from: 
/home/jenkins/.m2/repository/com/cenqua/clover/clover/3.0.2/clover-3.0.2.jar
[INFO] Clover: Open Source License registered to Apache.
[INFO] Clover is enabled with initstring 
'https://builds.apache.org/job/Hadoop-Common-0.23-Build/ws/trunk/hadoop-common-project/hadoop-auth/target/clover/hadoop-coverage.db'
[WARNING] Clover historical directory 
[https://builds.apache.org/job/Hadoop-Common-0.23-Build/ws/trunk/hadoop-common-project/hadoop-auth/target/clover/history]
 does not exist, skipping Clover historical report generation 
([https://builds.apache.org/job/Hadoop-Common-0.23-Build/ws/trunk/hadoop-common-project/hadoop-auth/target/clover])
[INFO] Clover Version 3.0.2, built on April 13 2010 (build-790)
[INFO] Loaded from: 
/home/jenkins/.m2/repository/com/cenqua/clover/clover/3.0.2/clover-3.0.2.jar
[INFO] Clover: Open Source License registered to Apache.
[INFO] Loading coverage database from: 
'https://builds.apache.org/job/Hadoop-Common-0.23-Build/ws/trunk/hadoop-common-project/hadoop-auth/target/clover/hadoop-coverage.db'
[INFO] Writing HTML report to 
'https://builds.apache.org/job/Hadoop-Common-0.23-Build/ws/trunk/hadoop-common-project/hadoop-auth/target/clover'
[INFO] Done. Processed 4 packages in 1091ms (272ms per package).
[INFO] Clover Version 3.0.2, built on April 13 2010 (build-790)
[INFO] Loaded from: 
/home/jenkins/.m2/repository/com/cenqua/clover/clover/3.0.2/clover-3.0.2.jar
[INFO] Clover: Open Source License registered to Apache.
[INFO] Clover is enabled with initstring 
'https://builds.apache.org/job/Hadoop-Common-0.23-Build/ws/trunk/hadoop-common-project/hadoop-auth/target/clover/hadoop-coverage.db'
[WARNING] Clover historical directory 
[https://builds.apache.org/job/Hadoop-Common-0.23-Build/ws/trunk/hadoop-common-project/hadoop-auth/target/clover/history]
 does not exist, skipping Clover historical report generation 
([https://builds.apache.org/job/Hadoop-Common-0.23-Build/ws/trunk/hadoop-common-project/hadoop-auth/target/clover/clover.xml])
[INFO] Clover Version 3.0.2, built on April 13 2010 (build-790)
[INFO] Loaded from: 
/home/jenkins/.m2/repository/com/cenqua/clover/clover/3.0.2/clover-3.0.2.jar
[INFO] Clover: Open Source License registered to Apache.
[INFO] Loading coverage database from: 
'https://builds.apache.org/job/Hadoop-Common-0.23-Build/ws/trunk/hadoop-common-project/hadoop-auth/target/clover/hadoop-coverage.db'
[INFO] Writing report to 
'https://builds.apache.org/job/Hadoop-Common-0.23-Build/ws/trunk/hadoop-common-project/hadoop-auth/target/clover/clover.xml'
[INFO] 
[INFO] 
[INFO] Building Apache Hadoop Auth Examples 0.23.5-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (create-testdirs) @ hadoop-auth-examples 
---
[INFO] Executing tasks

main:
[INFO] Executed tasks
[INFO] 
[INFO] --- maven-dependency-plugin:2.1:build-classpath (build-classpath) @ 
hadoop-auth-examples ---
[INFO] Wrote classpath file 
'https://builds.apache.org/job/Hadoop-Common-0.23-Build/ws/trunk/hadoop-common-project/hadoop-auth-examples/target/classes/mrapp-generated-classpath'.
[INFO] 
[INFO] --- maven-clover2-plugin:3.0.5:setup (setup) @ hadoop-auth-examples ---
[INFO] Clover Version 3.0.2, built on April 13 2010 (build-790)
[INFO] Loaded from: 
/home/jenkins/.m2/repository/com/cenqua/clover/clover/3.0.2/clover-3.0.2.jar
[INFO] Clover: Open Source License registered to Apache.
[INFO] Creating new database at 

[jira] [Created] (HADOOP-9002) repair test org.apache.hadoop.mapreduce.security.token.TestDelegationTokenRenewal

2012-11-01 Thread Ivan A. Veselovsky (JIRA)
Ivan A. Veselovsky created HADOOP-9002:
--

 Summary: repair test 
org.apache.hadoop.mapreduce.security.token.TestDelegationTokenRenewal
 Key: HADOOP-9002
 URL: https://issues.apache.org/jira/browse/HADOOP-9002
 Project: Hadoop Common
  Issue Type: Improvement
Reporter: Ivan A. Veselovsky
Assignee: Ivan A. Veselovsky


The test org.apache.hadoop.mapreduce.security.token.TestDelegationTokenRenewal 
is @Ignor-ed. 
Due to that several classes in package 
org.apache.hadoop.mapreduce.security.token have zero unit-test coverage.

The problem is that the test assumed that class 
org.apache.hadoop.mapreduce.security.token.TestDelegationTokenRenewal.Renewer 
is used as a custom implementation of the 
org.apache.hadoop.security.token.TokenRenewer service, but that did not happen, 
because this custom service implementation was not registered. 
We solved this problem by using special classloader that is invoked to find the 
resource META-INF/services/org.apache.hadoop.security.token.TokenRenewer , and 
supplies some custom content for it. This way the custom service implementation 
gets instantiated.

--
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] [Created] (HADOOP-9003) StringIntern not handling null correctly

2012-11-01 Thread Thomas Graves (JIRA)
Thomas Graves created HADOOP-9003:
-

 Summary: StringIntern not handling null correctly
 Key: HADOOP-9003
 URL: https://issues.apache.org/jira/browse/HADOOP-9003
 Project: Hadoop Common
  Issue Type: Improvement
Affects Versions: 0.23.4, 2.0.2-alpha, 3.0.0
Reporter: Thomas Graves
Assignee: Robert Joseph Evans
 Fix For: 2.0.3-alpha, 0.23.5


Tracking the change to StringIntern that went in with MAPREDUCE-4752 to fix the 
handling of null in StringIntern.

--
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] [Resolved] (HADOOP-9003) StringIntern not handling null correctly

2012-11-01 Thread Thomas Graves (JIRA)

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

Thomas Graves resolved HADOOP-9003.
---

   Resolution: Fixed
Fix Version/s: 3.0.0

This change went in with MAPREDUCE-4752.

 StringIntern not handling null correctly
 

 Key: HADOOP-9003
 URL: https://issues.apache.org/jira/browse/HADOOP-9003
 Project: Hadoop Common
  Issue Type: Improvement
Affects Versions: 3.0.0, 2.0.2-alpha, 0.23.4
Reporter: Thomas Graves
Assignee: Robert Joseph Evans
 Fix For: 3.0.0, 2.0.3-alpha, 0.23.5


 Tracking the change to StringIntern that went in with MAPREDUCE-4752 to fix 
 the handling of null in StringIntern.

--
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] [Reopened] (HADOOP-9003) StringIntern not handling null correctly

2012-11-01 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli reopened HADOOP-9003:
-


Reopening to set correct resolution.

 StringIntern not handling null correctly
 

 Key: HADOOP-9003
 URL: https://issues.apache.org/jira/browse/HADOOP-9003
 Project: Hadoop Common
  Issue Type: Improvement
Affects Versions: 3.0.0, 2.0.2-alpha, 0.23.4
Reporter: Thomas Graves
Assignee: Robert Joseph Evans
 Fix For: 3.0.0, 2.0.3-alpha, 0.23.5


 Tracking the change to StringIntern that went in with MAPREDUCE-4752 to fix 
 the handling of null in StringIntern.

--
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] [Resolved] (HADOOP-9003) StringIntern not handling null correctly

2012-11-01 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli resolved HADOOP-9003.
-

Resolution: Duplicate

Duplicate of MAPREDUCE-4752.

 StringIntern not handling null correctly
 

 Key: HADOOP-9003
 URL: https://issues.apache.org/jira/browse/HADOOP-9003
 Project: Hadoop Common
  Issue Type: Improvement
Affects Versions: 3.0.0, 2.0.2-alpha, 0.23.4
Reporter: Thomas Graves
Assignee: Robert Joseph Evans
 Fix For: 3.0.0, 2.0.3-alpha, 0.23.5


 Tracking the change to StringIntern that went in with MAPREDUCE-4752 to fix 
 the handling of null in StringIntern.

--
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] [Resolved] (HADOOP-8949) FileUtil.CygPathCommand is dead code on branch-1-win and branch-trunk-win

2012-11-01 Thread Suresh Srinivas (JIRA)

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

Suresh Srinivas resolved HADOOP-8949.
-

   Resolution: Fixed
Fix Version/s: trunk-win
   1-win
 Hadoop Flags: Reviewed

+1 for the patch. Committed to both branch-1-win and branch-trunk-win.

Thank you Chris.

 FileUtil.CygPathCommand is dead code on branch-1-win and branch-trunk-win
 -

 Key: HADOOP-8949
 URL: https://issues.apache.org/jira/browse/HADOOP-8949
 Project: Hadoop Common
  Issue Type: Task
  Components: fs
Affects Versions: 1-win, trunk-win
Reporter: Chris Nauroth
Assignee: Chris Nauroth
 Fix For: 1-win, trunk-win

 Attachments: HADOOP-8949-branch-1-win.patch, 
 HADOOP-8949-branch-trunk-win.patch


 We are converting to use winutils for Windows compatibility on external shell 
 commands.  With those changes in place, the FileUtil.CygPathCommand inner 
 class is no longer called.

--
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] [Resolved] (HADOOP-8956) FileSystem.primitiveMkdir failures on Windows cause multiple test suites to fail

2012-11-01 Thread Suresh Srinivas (JIRA)

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

Suresh Srinivas resolved HADOOP-8956.
-

   Resolution: Fixed
Fix Version/s: trunk-win
 Hadoop Flags: Reviewed

+1. I committed it branch-trunk-win.

Thank you Chris. Thank you Brandon for the review.

 FileSystem.primitiveMkdir failures on Windows cause multiple test suites to 
 fail
 

 Key: HADOOP-8956
 URL: https://issues.apache.org/jira/browse/HADOOP-8956
 Project: Hadoop Common
  Issue Type: Bug
  Components: fs
Affects Versions: trunk-win
Reporter: Chris Nauroth
Assignee: Chris Nauroth
 Fix For: trunk-win

 Attachments: HADOOP-8956-branch-trunk-win.patch, 
 HADOOP-8956-branch-trunk-win.patch, HADOOP-8956-branch-trunk-win.patch


 Multiple test suites fail on Windows in calls to FileSystem.primitiveMkdir.

--
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] [Resolved] (HADOOP-8978) TestTrash fails on Windows

2012-11-01 Thread Suresh Srinivas (JIRA)

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

Suresh Srinivas resolved HADOOP-8978.
-

   Resolution: Fixed
Fix Version/s: trunk-win
 Hadoop Flags: Reviewed

Chris thanks for the patch. +1. I committed it to branch-trunk-win.

 TestTrash fails on Windows
 --

 Key: HADOOP-8978
 URL: https://issues.apache.org/jira/browse/HADOOP-8978
 Project: Hadoop Common
  Issue Type: Bug
  Components: fs
Affects Versions: trunk-win
Reporter: Chris Nauroth
Assignee: Chris Nauroth
 Fix For: trunk-win

 Attachments: HADOOP-8978-branch-trunk-win.patch


 The tests assert that a file is found in trash after deleting, but it's not 
 found when run on Windows.

--
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] [Created] (HADOOP-9004) Allow security unit tests to use external KDC

2012-11-01 Thread Stephen Chu (JIRA)
Stephen Chu created HADOOP-9004:
---

 Summary: Allow security unit tests to use external KDC
 Key: HADOOP-9004
 URL: https://issues.apache.org/jira/browse/HADOOP-9004
 Project: Hadoop Common
  Issue Type: Improvement
  Components: security, test
Affects Versions: 2.0.0-alpha
Reporter: Stephen Chu
 Fix For: 3.0.0


I want to add the option of allowing security-related unit tests to use an 
external KDC.

In HADOOP-8078, we add the ability to start and use an ApacheDS KDC for 
security-related unit tests. It would be good to allow users to validate the 
use of their own KDC, keytabs, and principals and to test different KDCs and 
not rely on the ApacheDS KDC.

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