[jira] [Resolved] (HADOOP-13049) Fix the TestFailures After HADOOP-12563

2016-04-23 Thread Brahma Reddy Battula (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-13049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula resolved HADOOP-13049. --- Resolution: Duplicate HADOOP-12563 got reopen to address this failures,

Re: Looking to a Hadoop 3 release

2016-04-23 Thread Chris Douglas
If we're not starting branch-3/trunk, what would distinguish it from trunk/trunk-incompat? Is it the same mechanism with different labels? That may be a reasonable strategy when we create branch-3, as a release branch for beta. Releasing 3.x from trunk will help us figure out which

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1385

2016-04-23 Thread Apache Jenkins Server
See Changes: [iwasakims] HDFS-9905. WebHdfsFileSystem#runWithRetry should display original stack -- [...truncated 5631 lines...] Java HotSpot(TM) 64-Bit Server VM warning: ignoring

Re: [Release thread] 2.8.0 release activities

2016-04-23 Thread Steve Loughran
> On 23 Apr 2016, at 01:24, Vinod Kumar Vavilapalli wrote: > > We are not converging - there’s still 58 more. I need help from the community > in addressing / review 2.8.0 blockers. If folks can start with reviewing > Patch available tickets, that’ll be great. > > I'm

Re: Commit History Edit Alert

2016-04-23 Thread Steve Loughran
Force pushes break everyone who has been pulling them down, and has the potential to stamp on other people's changes that they got in between the original push and the commit. That's more common in PST than for us in the EU, who can work across all three branches without race conditions

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1384

2016-04-23 Thread Apache Jenkins Server
See Changes: [Arun Suresh] YARN-4335. Allow ResourceRequests to specify ExecutionType of a request -- [...truncated 5548 lines...] Running org.apache.hadoop.util.TestVersionUtil Tests