See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2137/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 32389 lines...]
[ERROR] To see the full stack trace
May we declare this branch dead and just close bugs (but not
necessarily concepts, ideas, etc) with won’t fix? I don’t think anyone has any
intention of working on the 1.3 release, especially given that 1.2.1 was Aug
2013 ….
I guess we need a PMC member to declare a
I think it would be fine to auto-close most remaining branch-1 issues
even if the branch is still formally considered alive. I don't expect us
to create a new 1.x release unless a security vulnerability or critical
bug forces it. Closing all non-critical issues would match with the
reality that
[
https://issues.apache.org/jira/browse/MAPREDUCE-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-41.
--
Resolution: Won't Fix
Long past when it was needed. Closing as Won't
[
https://issues.apache.org/jira/browse/MAPREDUCE-4672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-4672.
Resolution: Duplicate
bq. But when NM goes down, it doesn't
+1 to auto-closing branch-1 issues.
-Sandy
On Fri, May 8, 2015 at 11:14 AM, Karthik Kambatla ka...@cloudera.com
wrote:
Closing out the JIRAs as Auto Closed or Closed due to Inactivity seems
reasonable to me. For branch-1, we can be more aggressive. We should
probably do the same less
[
https://issues.apache.org/jira/browse/MAPREDUCE-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-5567.
Resolution: Fixed
Resolving this umbrella JIRA. RM restart has
[
https://issues.apache.org/jira/browse/MAPREDUCE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-1.
-
Resolution: Duplicate
Very old JIRA. Seems like a dup of HADOOP-6103 per
Closing out the JIRAs as Auto Closed or Closed due to Inactivity seems
reasonable to me. For branch-1, we can be more aggressive. We should
probably do the same less aggressively for other branches too.
On Fri, May 8, 2015 at 11:01 AM, Arun C Murthy acmur...@apache.org wrote:
+1
Arun
On May
[
https://issues.apache.org/jira/browse/MAPREDUCE-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-3945.
Resolution: Duplicate
This got fixed much later at
+1
Arun
On May 8, 2015, at 10:41 AM, Allen Wittenauer a...@altiscale.com wrote:
May we declare this branch dead and just close bugs (but not
necessarily concepts, ideas, etc) with won’t fix? I don’t think anyone has
any intention of working on the 1.3 release, especially
I would be -1 to declaring the branch dead just yet. There have been 7
commits to that branch this year. I know this isn't comparable to trunk or
branch-2, but it is not negligible either.
I propose we come up with a policy for deprecating past major release
branches. May be, something along the
[
https://issues.apache.org/jira/browse/MAPREDUCE-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-116.
---
Resolution: Won't Fix
Long past when it was needed.
The
[
https://issues.apache.org/jira/browse/MAPREDUCE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-97.
--
Resolution: Invalid
Very old JIRA.
With MRv2, we have largely also
Thank you Allen!
--Konst
On Tue, May 5, 2015 at 5:14 PM, Allen Wittenauer a...@altiscale.com wrote:
HDFS, MAPREDUCE, and YARN have been migrated.
Let me know of any issues and I’ll try to get to them as I can. This
should be the end of the Jenkins race conditions for our pre commits!
[
https://issues.apache.org/jira/browse/MAPREDUCE-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-3561.
Resolution: Fixed
I originally opened this to track performance
[
https://issues.apache.org/jira/browse/MAPREDUCE-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-3101.
Resolution: Fixed
Assignee: (was: Vinod Kumar
[
https://issues.apache.org/jira/browse/MAPREDUCE-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sunil G resolved MAPREDUCE-5617.
Resolution: Invalid
Yes Vinod.
I am marking this as invalid. I checked a similar scenario, and
Thanks Allen a lot for organizing the Haoop Bug Bash, very happy to see
many folks by face!
Wish you all a nice weekend!
--Yongjun
On Tue, May 5, 2015 at 9:31 PM, Allen Wittenauer a...@altiscale.com wrote:
On May 5, 2015, at 8:10 PM, Allen Wittenauer a...@altiscale.com wrote:
[
https://issues.apache.org/jira/browse/MAPREDUCE-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-5716.
Resolution: Invalid
Exit code 127 usually means that the
[
https://issues.apache.org/jira/browse/MAPREDUCE-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-5697.
Resolution: Invalid
Not sure if this is a real bug or not. In
[
https://issues.apache.org/jira/browse/MAPREDUCE-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-5563.
Resolution: Invalid
It passes now on trunk for me too. Closing
[
https://issues.apache.org/jira/browse/MAPREDUCE-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-5582.
Resolution: Won't Fix
We haven't done a 1.x release in ~2
[
https://issues.apache.org/jira/browse/MAPREDUCE-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-5703.
Resolution: Duplicate
I have run into the same problem many
[
https://issues.apache.org/jira/browse/MAPREDUCE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-472.
---
Resolution: Won't Fix
We haven't done a 1.x release in ~2 years.
[
https://issues.apache.org/jira/browse/MAPREDUCE-2759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-2759.
Resolution: Won't Fix
We haven't done a 1.x/0.21/0.22 based
[
https://issues.apache.org/jira/browse/MAPREDUCE-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-2769.
Resolution: Won't Fix
We haven't done a 1.x/0.21/0.22 based
[
https://issues.apache.org/jira/browse/MAPREDUCE-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-5606.
Resolution: Won't Fix
I originally debugged the user.location
[
https://issues.apache.org/jira/browse/MAPREDUCE-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-5903.
Resolution: Invalid
My comment
[
https://issues.apache.org/jira/browse/MAPREDUCE-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-2049.
Resolution: Won't Fix
We haven't done a 1.x/0.21/0.22 based
[
https://issues.apache.org/jira/browse/MAPREDUCE-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-1396.
Resolution: Won't Fix
We haven't done a 1.x release in ~2
[
https://issues.apache.org/jira/browse/MAPREDUCE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-488.
---
Resolution: Won't Fix
We haven't done a 1.x release in ~2 years.
32 matches
Mail list logo