See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/1388/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 9269 lines...]
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/3307/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 32738 lines...]
[INFO] ---
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/1387/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 9541 lines...]
Running
For MapReduce/YARN, I closed a few staled ones. Only 4 jiras needs attention
for 2.8
MAPREDUCE-6288
YARN-1815
YARN-4685
YARN-4844
The rest are either improvements or long-standing issues and does not qualify
release blocker, IMO.
I think we’ll try to get these 4 jiras in asap. The rest will be
I see the following list of JIRAs from HADOOP and HDFS as blockers for
2.8.0. Other JIRAs are either old issues with little movement or new issues
that don't appear to be as critical/ready.
- HADOOP-12893
- HADOOP-12892
- HADOOP-10940 (patch ready?)
- HADOOP-12971 (can be done relatively
Sounds good to me :).
Jian and I have looked at all existing 2.8.0 blockers and criticals today.
To me more than half of MR/YARN blockers/criticals of 2.8 should be moved
out. Left comments on these JIRAs asked original owners, plan to update
target version of these JIRAs early next week.
Will
How about this? I'll review the HADOOP/HDFS bugs in that list to come up
with true blockers for 2.8.0 or JIRAs that are close to being ready. I'll
report the list here. Then folks can chime in if you agree
Perhaps Wangda, you can go over the YARN/MR bugs. Sound like a plan?
Thanks,
Sangjin
On
[
https://issues.apache.org/jira/browse/MAPREDUCE-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jian He resolved MAPREDUCE-6099.
Resolution: Won't Fix
Close as Jason mentioned
> Adding getSplits(JobContext job, List
+1, we should close such staled JIRAs to avoid doing unnecessary checks for
every releases.
I'm working on reviewing YARN/MR critical/blocker patches currently, it
gonna very helpful if someone else can help with reviewing Common/HDFS
JIRAs.
Thanks,
Wangda
On Wed, May 11, 2016 at 4:20 PM,
Where do we stand in terms of closing out blocker/critical issues for
2.8.0? I still see 50 open JIRAs in Vinod's list:
https://issues.apache.org/jira/issues/?filter=12334985
But I see a lot of JIRAs with no patches or very stale patches. It would be
a good exercise to come up with the list of
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/1386/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 8921 lines...]
Tests run: 9, Failures: 0,
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/3306/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 32405 lines...]
[INFO] ---
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/1385/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 15097 lines...]
Tests run: 5, Failures: 0,
bq. We'll need to be strict after the switch: all patches to go into branch 2
will have to go through yetus as branch-2 patches, then cherry picked to trunk,
or a separate patch on the same JIRA done for the branch-2. Assuming yetus
still tests the branch-2 stuff on JDK7, that will check
>
> On 10 May 2016, at 16:32, Akira AJISAKA wrote:
>
> Hi developers,
>
> Before cutting 3.0.0-alpha RC, I'd like to drop JDK7 support in trunk.
+1
Given Robert Kanter first filed the patch to do this —why not give him the
honour. In fact, why not have a webex
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/1384/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 9513 lines...]
Running
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/3304/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 32132 lines...]
[INFO] ---
+1 (non-binding)
reviewed everything, filed an additional subtask for a very trivial
typo in the docs. should be fine to make a full issue after close and
then fix.
tried merging locally, tried running through new shell tests (both
with and without bats installed), tried making an example custom
18 matches
Mail list logo