Build failed in Jenkins: Hadoop-Common-trunk #533

2012-09-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Common-trunk/533/changes

Changes:

[atm] HADOOP-8755. Print thread dump when tests fail due to timeout. 
Contributed by Andrey Klochkov.

[atm] HDFS-3924. Multi-byte id in HdfsVolumeId. Contributed by Andrew Wang.

[atm] HADOOP-8795. BASH tab completion doesn't look in PATH, assumes path to 
executable is specified. Contributed by Sean Mackrory.

[eli] HADOOP-8801. ExitUtil#terminate should capture the exception stack trace. 
Contributed by Eli Collins

--
[...truncated 26481 lines...]
[DEBUG]   (s) debug = false
[DEBUG]   (s) effort = Default
[DEBUG]   (s) failOnError = true
[DEBUG]   (s) findbugsXmlOutput = false
[DEBUG]   (s) findbugsXmlOutputDirectory = 
https://builds.apache.org/job/Hadoop-Common-trunk/ws/trunk/hadoop-common-project/target
[DEBUG]   (s) fork = true
[DEBUG]   (s) includeTests = false
[DEBUG]   (s) localRepository =id: local
  url: file:///home/jenkins/.m2/repository/
   layout: none

[DEBUG]   (s) maxHeap = 512
[DEBUG]   (s) nested = false
[DEBUG]   (s) outputDirectory = 
https://builds.apache.org/job/Hadoop-Common-trunk/ws/trunk/hadoop-common-project/target/site
[DEBUG]   (s) outputEncoding = UTF-8
[DEBUG]   (s) pluginArtifacts = 
[org.codehaus.mojo:findbugs-maven-plugin:maven-plugin:2.3.2:, 
com.google.code.findbugs:bcel:jar:1.3.9:compile, 
org.codehaus.gmaven:gmaven-mojo:jar:1.3:compile, 
org.codehaus.gmaven.runtime:gmaven-runtime-api:jar:1.3:compile, 
org.codehaus.gmaven.feature:gmaven-feature-api:jar:1.3:compile, 
org.codehaus.gmaven.runtime:gmaven-runtime-1.5:jar:1.3:compile, 
org.codehaus.gmaven.feature:gmaven-feature-support:jar:1.3:compile, 
org.codehaus.groovy:groovy-all-minimal:jar:1.5.8:compile, 
org.apache.ant:ant:jar:1.7.1:compile, 
org.apache.ant:ant-launcher:jar:1.7.1:compile, jline:jline:jar:0.9.94:compile, 
org.codehaus.plexus:plexus-interpolation:jar:1.1:compile, 
org.codehaus.gmaven:gmaven-plugin:jar:1.3:compile, 
org.codehaus.gmaven.runtime:gmaven-runtime-loader:jar:1.3:compile, 
org.codehaus.gmaven.runtime:gmaven-runtime-support:jar:1.3:compile, 
org.sonatype.gshell:gshell-io:jar:2.0:compile, 
com.thoughtworks.qdox:qdox:jar:1.10:compile, 
org.apache.maven.shared:file-management:jar:1.2.1:compile, 
org.apache.maven.shared:maven-shared-io:jar:1.1:compile, 
commons-lang:commons-lang:jar:2.4:compile, 
org.slf4j:slf4j-api:jar:1.5.10:compile, 
org.sonatype.gossip:gossip:jar:1.2:compile, 
org.apache.maven.reporting:maven-reporting-impl:jar:2.1:compile, 
commons-validator:commons-validator:jar:1.2.0:compile, 
commons-beanutils:commons-beanutils:jar:1.7.0:compile, 
commons-digester:commons-digester:jar:1.6:compile, 
commons-logging:commons-logging:jar:1.0.4:compile, oro:oro:jar:2.0.8:compile, 
xml-apis:xml-apis:jar:1.0.b2:compile, 
org.codehaus.groovy:groovy-all:jar:1.7.4:compile, 
org.apache.maven.reporting:maven-reporting-api:jar:3.0:compile, 
org.apache.maven.doxia:doxia-core:jar:1.1.3:compile, 
org.apache.maven.doxia:doxia-logging-api:jar:1.1.3:compile, 
xerces:xercesImpl:jar:2.9.1:compile, 
commons-httpclient:commons-httpclient:jar:3.1:compile, 
commons-codec:commons-codec:jar:1.2:compile, 
org.apache.maven.doxia:doxia-sink-api:jar:1.1.3:compile, 
org.apache.maven.doxia:doxia-decoration-model:jar:1.1.3:compile, 
org.apache.maven.doxia:doxia-site-renderer:jar:1.1.3:compile, 
org.apache.maven.doxia:doxia-module-xhtml:jar:1.1.3:compile, 
org.apache.maven.doxia:doxia-module-fml:jar:1.1.3:compile, 
org.codehaus.plexus:plexus-i18n:jar:1.0-beta-7:compile, 
org.codehaus.plexus:plexus-velocity:jar:1.1.7:compile, 
org.apache.velocity:velocity:jar:1.5:compile, 
commons-collections:commons-collections:jar:3.2:compile, 
org.apache.maven.shared:maven-doxia-tools:jar:1.2.1:compile, 
commons-io:commons-io:jar:1.4:compile, 
com.google.code.findbugs:findbugs-ant:jar:1.3.9:compile, 
com.google.code.findbugs:findbugs:jar:1.3.9:compile, 
com.google.code.findbugs:jsr305:jar:1.3.9:compile, 
com.google.code.findbugs:jFormatString:jar:1.3.9:compile, 
com.google.code.findbugs:annotations:jar:1.3.9:compile, 
dom4j:dom4j:jar:1.6.1:compile, jaxen:jaxen:jar:1.1.1:compile, 
jdom:jdom:jar:1.0:compile, xom:xom:jar:1.0:compile, 
xerces:xmlParserAPIs:jar:2.6.2:compile, xalan:xalan:jar:2.6.0:compile, 
com.ibm.icu:icu4j:jar:2.6.1:compile, asm:asm:jar:3.1:compile, 
asm:asm-analysis:jar:3.1:compile, asm:asm-commons:jar:3.1:compile, 
asm:asm-util:jar:3.1:compile, asm:asm-tree:jar:3.1:compile, 
asm:asm-xml:jar:3.1:compile, jgoodies:plastic:jar:1.2.0:compile, 
org.codehaus.plexus:plexus-resources:jar:1.0-alpha-4:compile, 
org.codehaus.plexus:plexus-utils:jar:1.5.1:compile]
[DEBUG]   (s) project = MavenProject: 
org.apache.hadoop:hadoop-common-project:3.0.0-SNAPSHOT @ 
https://builds.apache.org/job/Hadoop-Common-trunk/ws/trunk/hadoop-common-project/pom.xml
[DEBUG]   (s) relaxed = false
[DEBUG]   (s) remoteArtifactRepositories = [   id: apache.snapshots.https
  url: 

[jira] [Created] (HADOOP-8809) RPMs should skip useradds if the users already exist

2012-09-14 Thread Steve Loughran (JIRA)
Steve Loughran created HADOOP-8809:
--

 Summary: RPMs should skip useradds if the users already exist
 Key: HADOOP-8809
 URL: https://issues.apache.org/jira/browse/HADOOP-8809
 Project: Hadoop Common
  Issue Type: Bug
  Components: scripts
Affects Versions: 1.0.3
Reporter: Steve Loughran
Priority: Minor


The hadoop.spec preinstall script creates users -but it does this even if they 
already exist. This may causes problems if the installation has already got 
those users with different uids. A check with {{id}} can avoid this.

--
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-8799) commons-lang version mismatch

2012-09-14 Thread Joel Costigliola (JIRA)

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

Joel Costigliola resolved HADOOP-8799.
--

Resolution: Invalid

 commons-lang version mismatch
 -

 Key: HADOOP-8799
 URL: https://issues.apache.org/jira/browse/HADOOP-8799
 Project: Hadoop Common
  Issue Type: Bug
  Components: build
Affects Versions: 1.0.3
Reporter: Joel Costigliola

 hadoop install references commons-lang-2.4.jar while hadoop-core dependency 
 references commons-lang:jar:2.6 as shown in maven dependency:tree command 
 output extract.
 {noformat}
 org.apache.hadoop:hadoop-core:jar:1.0.3:provided
 +- commons-cli:commons-cli:jar:1.2:provided
 +- xmlenc:xmlenc:jar:0.52:provided
 +- commons-httpclient:commons-httpclient:jar:3.0.1:provided
 +- commons-codec:commons-codec:jar:1.4:provided
 +- org.apache.commons:commons-math:jar:2.1:provided
 +- commons-configuration:commons-configuration:jar:1.6:provided
 |  +- commons-collections:commons-collections:jar:3.2.1:provided
 |  +- commons-lang:commons-lang:jar:2.6:provided (version managed from 2.4)
 {noformat}
 Hadoop install libs should be consistent with hadoop-core maven dependencies.
 I found this error because I was using a feature available in 
 commons-lang.2.6 that was failing when executed in my hadoop cluster (but not 
 with m pigunit tests).
 A last remark, it would be nice to display the classpath used by hadoop 
 cluster while executing a job, because these kinds of errors are not easy to 
 find.

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


Test timeouts

2012-09-14 Thread Aaron T. Myers
Hello devs,

With the commit of HADOOP-8755, we now have support for printing a thread
dump whenever a test case times out. However, this will only happen for
test cases which are annotated with a JUnit timeout, i.e. those annotated
with something like @Test(timeout=X). Unfortunately, there doesn't seem
to be an easy way to add a default JUnit timeout for all of our tests, so
some tests may time out by reaching the Surefire fork timeout, in which
case the thread dump will not be printed. You can see more discussion about
this on HADOOP-8755.

So, if you see a test case fail by reaching the Surefire fork timeout,
please file a JIRA to add a JUnit timeout for that test. If when adding a
test case you think that it might time out, please add a JUnit timeout.

Thanks,
Aaron

--
Aaron T. Myers
Software Engineer, Cloudera


[jira] [Resolved] (HADOOP-8734) LocalJobRunner does not support private distributed cache

2012-09-14 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli resolved HADOOP-8734.
-

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

+1, looks good. Verified that the test fails without the code change and passes 
with.

Just committed this to branch-1-win. Thanks Ivan!

 LocalJobRunner does not support private distributed cache
 -

 Key: HADOOP-8734
 URL: https://issues.apache.org/jira/browse/HADOOP-8734
 Project: Hadoop Common
  Issue Type: Bug
  Components: filecache
Reporter: Ivan Mitic
Assignee: Ivan Mitic
 Fix For: 1-win

 Attachments: HADOOP-8734-LocalJobRunner.patch


 It seems that LocalJobRunner does not support private distributed cache. The 
 issue is more visible on Windows as all DC files are private by default (see 
 HADOOP-8731).

--
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-8810) when building with documentation build stops waiting for ENTER on terminal

2012-09-14 Thread Alejandro Abdelnur (JIRA)
Alejandro Abdelnur created HADOOP-8810:
--

 Summary: when building with documentation build stops waiting for 
ENTER on terminal
 Key: HADOOP-8810
 URL: https://issues.apache.org/jira/browse/HADOOP-8810
 Project: Hadoop Common
  Issue Type: Improvement
  Components: build
Affects Versions: 2.0.3-alpha
Reporter: Alejandro Abdelnur
Assignee: Alejandro Abdelnur
 Fix For: 2.0.3-alpha


When building the docs {{mvn clean package -Pdocs -DskipTests site site:stage 
-DstagingDirectory=/tmp/hadoop-site}}, in OSX (and I've seen it a few times in 
Ubuntu as well), the build stops, if you press ENTER it continues. It happens 
twice.

I've traced this down to the exec-maven-plugin invocation of protoc for 
hadoop-yarn-api module (and other YARN module I don't recall at the moment).

jstacking the Maven process it seems the exec-maven-plugin has some locking 
issues consuming the STDOUT/STDERR of the process being executed.

I've converted the protoc invocation in the hadoop-yarn-api to use the antrun 
plugin instead and then another module running protoc using exec-maven-puglin 
hang.




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


Re: update re: Hadoop-1.1.0-rc0

2012-09-14 Thread Bhandarkar, Milind

- MAPREDUCE-4049 - plugin for generic shuffle service

Committers,

What else is needed on MR-4049 to commit ?

- milind





Re: Test timeouts

2012-09-14 Thread Todd Lipcon
On Fri, Sep 14, 2012 at 11:23 AM, Aaron T. Myers a...@cloudera.com wrote:

 So, if you see a test case fail by reaching the Surefire fork timeout,
 please file a JIRA to add a JUnit timeout for that test. If when adding a
 test case you think that it might time out, please add a JUnit timeout.

I'd go one step further:
If you add any test that isn't a true unit test (ie it relies on any
mulithreading, either explicitly or by using miniclusters, etc), you
should add a timeout. Even if it has to be conservative (like 5
minutes on a test that you expect only runs 10 seconds), it seems
better than waiting for it to timeout and then later having to go back
and add one.

-Todd
-- 
Todd Lipcon
Software Engineer, Cloudera


[jira] [Created] (HADOOP-8812) ExitUtil#terminate should print Exception#toString

2012-09-14 Thread Eli Collins (JIRA)
Eli Collins created HADOOP-8812:
---

 Summary: ExitUtil#terminate should print Exception#toString 
 Key: HADOOP-8812
 URL: https://issues.apache.org/jira/browse/HADOOP-8812
 Project: Hadoop Common
  Issue Type: Improvement
Affects Versions: 2.0.2-alpha
Reporter: Eli Collins
Assignee: Eli Collins
Priority: Minor


Per Steve's feedback on ExitUtil#terminate should print Exception#toString 
rather than use getMessage as the latter may return null.  

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