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/ https://builds.apache.org/job/PreCommit-YARN-Build/5039//testReport/Findbugs warnings: https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/newPatchFindbugsWarningshadoop-yarn-client.htmlJavac warnings: https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/diffJavacWarnings.txt https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/diffJavacWarnings.txt* It will report 404 when trying to access findbugs/javac warnings and it will redirect to info page of build when trying to access test report. I'm not sure if there's any recent changes on Jenkins configuration. Did you hit the problem like this? Thanks, Wangda
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 wheele...@gmail.com wrote: 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/ https://builds.apache.org/job/PreCommit-YARN-Build/5039//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html Javac warnings: https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/diffJavacWarnings.txt https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/diffJavacWarnings.txt * It will report 404 when trying to access findbugs/javac warnings and it will redirect to info page of build when trying to access test report. I'm not sure if there's any recent changes on Jenkins configuration. Did you hit the problem like this? Thanks, Wangda -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
[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
Issue Type: Improvement
Components: tools
Reporter: Steve Loughran
Assignee: Steve Loughran
Priority: Minor
The miniKDC cluster uses {{.equalsIgnoreCase()}}, and {{.toLower()}},
{{.toUpper}} everywhere. While nobody uses this in production, it should be
fixed to ensure tests run consistently across all locales.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[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
-
Key: HADOOP-11084
URL: https://issues.apache.org/jira/browse/HADOOP-11084
Project: Hadoop Common
Issue Type: New Feature
Components: scripts
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe
Fix For: 2.6.0
Attachments: HADOOP-11084.001.patch
jenkins patchprocess links of the form
{{https://builds.apache.org/job/PreCommit-HADOOP-Build/build_id//artifact/trunk/patchprocess/diffJavadocWarnings.txt}}
and so forth are dead links. We should fix them to reflect the new source
layout after git.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
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 ste...@hortonworks.com wrote: 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 wheele...@gmail.com wrote: 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/ https://builds.apache.org/job/PreCommit-YARN-Build/5039//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html Javac warnings: https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/diffJavacWarnings.txt https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/diffJavacWarnings.txt * It will report 404 when trying to access findbugs/javac warnings and it will redirect to info page of build when trying to access test report. I'm not sure if there's any recent changes on Jenkins configuration. Did you hit the problem like this? Thanks, Wangda -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
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 if it takes On 19 September 2014 10:54, Wangda Tan wheele...@gmail.com wrote: 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 ste...@hortonworks.com wrote: 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 wheele...@gmail.com wrote: 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/ https://builds.apache.org/job/PreCommit-YARN-Build/5039//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html Javac warnings: https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/diffJavacWarnings.txt https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/diffJavacWarnings.txt * It will report 404 when trying to access findbugs/javac warnings and it will redirect to info page of build when trying to access test report. I'm not sure if there's any recent changes on Jenkins configuration. Did you hit the problem like this? Thanks, Wangda -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
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 wheele...@gmail.com wrote: 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 ste...@hortonworks.com wrote: 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 wheele...@gmail.com wrote: 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/ https://builds.apache.org/job/PreCommit-YARN-Build/5039//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html Javac warnings: https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/diffJavacWarnings.txt https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/diffJavacWarnings.txt * It will report 404 when trying to access findbugs/javac warnings and it will redirect to info page of build when trying to access test report. I'm not sure if there's any recent changes on Jenkins configuration. Did you hit the problem like this? Thanks, Wangda -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
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? Colin On Fri, Sep 19, 2014 at 5:42 AM, Steve Loughran ste...@hortonworks.com wrote: 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 if it takes On 19 September 2014 10:54, Wangda Tan wheele...@gmail.com wrote: 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 ste...@hortonworks.com wrote: 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 wheele...@gmail.com wrote: 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/ https://builds.apache.org/job/PreCommit-YARN-Build/5039//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html Javac warnings: https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/diffJavacWarnings.txt https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/diffJavacWarnings.txt * It will report 404 when trying to access findbugs/javac warnings and it will redirect to info page of build when trying to access test report. I'm not sure if there's any recent changes on Jenkins configuration. Did you hit the problem like this? Thanks, Wangda -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
[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
Issue Type: Bug
Components: security
Affects Versions: 2.6.0
Reporter: Alejandro Abdelnur
Assignee: Alejandro Abdelnur
Attachments: HADOOP-2.patch
HDFS-7004 missed updating {{TestKMSWithZK}} to use {{KEY_PROVIDER_URI}} to set
the keyprovider URI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
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 things work than the other way around. On Thu, Sep 18, 2014 at 2:40 PM, Steve Loughran ste...@hortonworks.com wrote: I know we've been ignoring the Guava version problem, but HADOOP-10868 added a transitive dependency on Guava 16 by way of Curator 2.6. Maven currently forces the build to use Guava 11.0.2, but this is hiding at compile timeall code paths from curator which may use classes methods that aren't there. I need curator for my own work (2.4.1 Guava 14.0 was what I'd been using), so don't think we can go back. HADOOP-11102 covers the problem -but doesn't propose a specific solution. But to me the one that seems most likely to work is: update Guava -steve -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
