[jira] [Resolved] (HADOOP-5628) Create target for 10 minute patch test build

[ https://issues.apache.org/jira/browse/HADOOP-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-5628. -- Resolution: Invalid Closing this as stale. test-patch.sh is now very smart about what

[jira] [Resolved] (HADOOP-7790) hadoop-yarn-api - generate-sources build step waits for input

[ https://issues.apache.org/jira/browse/HADOOP-7790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-7790. -- Resolution: Cannot Reproduce Closing as stale. > hadoop-yarn-api - generate-sources bu

[jira] [Resolved] (HADOOP-7620) All profiles should build the javadoc

[ https://issues.apache.org/jira/browse/HADOOP-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-7620. -- Resolution: Won't Fix Closing as won't fix. test-patch has been much better about testi

[jira] [Resolved] (HADOOP-7107) Ability to retrigger Hudson QA bot without re-uploading patch

[ https://issues.apache.org/jira/browse/HADOOP-7107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-7107. -- Resolution: Implemented Cancel+submit pair usually works. Closing as implemented. > Ab

[jira] [Resolved] (HADOOP-11320) Submitting a hadoop patch doesn't trigger jenkins test run

[ https://issues.apache.org/jira/browse/HADOOP-11320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-11320. --- Resolution: Fixed Based upon the previous discussion, it looks as though this should

[jira] [Resolved] (HADOOP-6282) test-patch should verify that FindBugs version used for verification is correct one

[ https://issues.apache.org/jira/browse/HADOOP-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-6282. -- Resolution: Implemented Closing as FindBugs is now implemented via maven. However it s

[jira] [Resolved] (HADOOP-6256) Update comments in test-patch.sh to clarify changes done in HADOOP-6250

[ https://issues.apache.org/jira/browse/HADOOP-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-6256. -- Resolution: Won't Fix HADOOP-11746 removed this code since it hasn't been in use for a

[jira] [Resolved] (HADOOP-7670) test-patch should not -1 for just build changes

[ https://issues.apache.org/jira/browse/HADOOP-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-7670. -- Resolution: Implemented This is pretty much what HADOOP-11746 does. Closing as impleme

[jira] [Resolved] (HADOOP-8483) test-patch +1 even there are build failures

[ https://issues.apache.org/jira/browse/HADOOP-8483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-8483. -- Resolution: Invalid Closing as stale. > test-patch +1 even there are build failures >

[jira] [Resolved] (HADOOP-6300) Increase maxwarns for javac in test-patch

[ https://issues.apache.org/jira/browse/HADOOP-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-6300. -- Resolution: Won't Fix A different method for dealing with warnings has been implemented

[jira] [Resolved] (HADOOP-8344) Improve test-patch to make it easier to find javadoc warnings

[ https://issues.apache.org/jira/browse/HADOOP-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-8344. -- Resolution: Implemented This has been implemented already. Closing. > Improve test-pat

[jira] [Resolved] (HADOOP-8875) test-patch.sh doesn't test changes to itself

[ https://issues.apache.org/jira/browse/HADOOP-8875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-8875. -- Resolution: Implemented > test-patch.sh doesn't test changes to itself > --

Bug Bash Details/Registration: May 8th, 2015

(Reply-to set to common-dev@) With over 900 patches not yet reviewed and approved for Apache Hadoop, it's time to make some strong progress on the bug list! A number of Apache Hadoop committers and Hadoop-related tech companies are hosting an Apache Hadoop Community event on Fri

Re: [ANNOUNCE] Apache Hadoop 2.7.0 Release

No, I did use JIRA filters. But got some very weird results - likely because I was editing my blockers-only search filter and forgot to unselect some conditions. +Vinod On Apr 25, 2015, at 7:11 AM, Allen Wittenauer wrote: > > On Apr 24, 2015, at 11:41 PM, Vinod Kumar Vavilapalli > wrote: >

Re: [DISCUSS] Release numbering for stable 2.8 and beyond

I don't think it makes sense to imprint the release quality with its version. They should be separate. And our recommendation for the quality can be reflected in the documentation. (1) is the way to go. We had "alpha" imprinted in 2.0.5-alpha version, but both 2.0.5 and 2.0.6 releases were quite s

Re: [ANNOUNCE] Apache Hadoop 2.7.0 Release

On Apr 24, 2015, at 11:41 PM, Vinod Kumar Vavilapalli wrote: > > Marco Zühlke pinged me offline informing me that I completely got my > issue-count wrong. > > Seems like I had a very bizarre filter, I missed closing some tickets too at > release time. You were probably counting cha

[jira] [Created] (HADOOP-11877) SnappyDecompressor's Logger class name is wrong

surendra singh lilhore created HADOOP-11877: --- Summary: SnappyDecompressor's Logger class name is wrong Key: HADOOP-11877 URL: https://issues.apache.org/jira/browse/HADOOP-11877 Project: Hadoo