[jira] [Created] (HADOOP-11113) Namenode not able to reconnect to KMS after KMS restart

Arun Suresh created HADOOP-3: Summary: Namenode not able to reconnect to KMS after KMS restart Key: HADOOP-3 URL: https://issues.apache.org/jira/browse/HADOOP-3 Project: Hadoop Common

Re: Time to address the Guava version problem

I would also agree on upgrading guava. Yes I am aware of the potential impact on customers who might rely on hadoop bringing in guava 11. However, IMHO the balance tipped over to the other side a while ago; i.e. I think there are far more people using guava 16 in their code and scrambling to make t

[jira] [Created] (HADOOP-11112) TestKMSWithZK does not use KEY_PROVIDER_URI

Alejandro Abdelnur created HADOOP-2: --- Summary: TestKMSWithZK does not use KEY_PROVIDER_URI Key: HADOOP-2 URL: https://issues.apache.org/jira/browse/HADOOP-2 Project: Hadoop Common

Re: Cannot access Jenkins generated test results, findbug warnings and javac warnings

patchprocess has always lived inside the workspace, now that we have moved to git and the test-patch script does a git reset and git clean it removes the patchprocess directory. so I put a fix to create the patchprocess dir outside the workspace and move it back into workspace soon after the build

Re: Cannot access Jenkins generated test results, findbug warnings and javac warnings

Thanks, Steve. Should we just put everything in patchprocess/ like before? It seems like renaming this directory to PreCommit-HADOOP-Build-patchprocess/ or PreCommit-YARN-Build-patchprocess/ in various builds has created problems, and not made things any more clear. What do you guys think? Coli

Re: Cannot access Jenkins generated test results, findbug warnings and javac warnings

Wangda: In the meantime, you can find the failed unit test from console log. e.g.: https://builds.apache.org/job/PreCommit-YARN-Build/5040/console Then you can run the test locally to see if the failure was related to your patch. Cheers On Fri, Sep 19, 2014 at 2:54 AM, Wangda Tan wrote: > Hi

Re: Cannot access Jenkins generated test results, findbug warnings and javac warnings

well, I have those permissions, but not sure where things are going right now 1. jenkins is set to archive patchprocess/*.* 1 & publish tests from trunk/**/target/surefire-reports/*.xml I've set it to use the path PreCommit-HADOOP-Build-patchprocess/*.* & will do some manual triggering to see i

Re: Cannot access Jenkins generated test results, findbug warnings and javac warnings

Hi Steve, I guess this problem should be also caused by wrong URL, if anybody have admin access to Jenkins, correct URL should be easily found. Thanks, Wangda On Fri, Sep 19, 2014 at 4:32 PM, Steve Loughran wrote: > Looks like HADOOP-11084 isn't complete —the patch to the build to get it > work

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

See -- [...truncated 10737 lines...] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.218 sec Running org.apache.hadoop.metrics2.impl.TestGangliaMetrics Tests run: 2, Failures: 0

[jira] [Reopened] (HADOOP-11084) jenkins patchprocess links are broken

[ https://issues.apache.org/jira/browse/HADOOP-11084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran reopened HADOOP-11084: - > jenkins patchprocess links are broken > - > >

[jira] [Created] (HADOOP-11111) MiniKDC to use locale EN_US for case conversions

Steve Loughran created HADOOP-1: --- Summary: MiniKDC to use locale EN_US for case conversions Key: HADOOP-1 URL: https://issues.apache.org/jira/browse/HADOOP-1 Project: Hadoop Common

Re: Cannot access Jenkins generated test results, findbug warnings and javac warnings

Looks like HADOOP-11084 isn't complete —the patch to the build to get it working post-git before that patch the builds weren't working at all ... now its just getting the URLs wrong. If you can work out the right URLs we can fix this easily enough On 19 September 2014 09:24, Wangda Tan wrote:

Cannot access Jenkins generated test results, findbug warnings and javac warnings

Hi Hadoop developers, I found recently, I cannot access Jenkins generated results, like: *Test results: https://builds.apache.org/job/PreCommit-YARN-Build/5039//testReport/ Findbugs warnings: https://builds.apache.org/job/Pre