Build failed in Jenkins: Hadoop-Common-trunk #1932

See Changes: [sjlee] Updated the 2.6.2 final release date. -- [...truncated 5398 lines...] Running org.apache.hadoop.fs.contract.rawlocal.TestRawlocalContractAppend Tests run: 5, Failures: 0,

Jenkins build is back to normal : Hadoop-common-trunk-Java8 #632

See

Re: Github integration for Hadoop

Thanks Owen. I'll volunteer myself and Colin to review the docs when you put them together. Regarding open q's, from my earlier email: = Great, glad to hear it. That wasn't mentioned in the email thread or on the INFRA ticket, and the INFRA ticket mentions these integrations: Commit Comment

Re: Github integration for Hadoop

On Fri, Oct 30, 2015 at 2:37 PM, Andrew Wang wrote: > > Strongly agree that we need documentation for all this. Agreed. > Some of my open questions are also still pending. > Which open questions? Owen, are you chasing all of this down? Do we need some JIRAs to track? > Yeah, I'll take a fi

[jira] [Created] (HADOOP-12535) Run FileSystem contract tests with hadoop-azure.

Chris Nauroth created HADOOP-12535: -- Summary: Run FileSystem contract tests with hadoop-azure. Key: HADOOP-12535 URL: https://issues.apache.org/jira/browse/HADOOP-12535 Project: Hadoop Common

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

See Changes: [kihwal] MAPREDUCE-6451. DistCp has incorrect chunkFilePath for multiple jobs [kihwal] Addendum to MAPREDUCE-6451 -- [...truncated 5887 lines...] Tests run: 1, Failures: 0,

Jenkins build is back to normal : Hadoop-Common-trunk #1931

See

Re: Github integration for Hadoop

On Fri, Oct 30, 2015 at 1:59 PM, Colin P. McCabe wrote: > I am -1 on the current GH stuff, just because I feel like there wasn't > enough discussion, testing, and documentation of it. The initial > proposal had no details and was implemented before any of the people > who had had misgivings on t

Re: Github integration for Hadoop

I am -1 on the current GH stuff, just because I feel like there wasn't enough discussion, testing, and documentation of it. The initial proposal had no details and was implemented before any of the people who had had misgivings on the previous email thread had a chance to even see it. It's a big

Build failed in Jenkins: Hadoop-Common-trunk #1930

See Changes: [aw] HADOOP-12133 Add schemas to Maven Assembly XMLs -- [...truncated 8546 lines...] [javadoc] Loading source files for package org.apache.hadoop.log.metrics... [javadoc] Loa

[jira] [Created] (HADOOP-12534) User document for SFTP File System

ramtin created HADOOP-12534: --- Summary: User document for SFTP File System Key: HADOOP-12534 URL: https://issues.apache.org/jira/browse/HADOOP-12534 Project: Hadoop Common Issue Type: Improvement

Jenkins build is back to normal : Hadoop-common-trunk-Java8 #629

See

Re: Github integration for Hadoop

On Fri, Oct 30, 2015 at 1:22 PM, Allen Wittenauer wrote: > >> * Have we tried our precommit on PRs yet? Does it work for multiple >> branches? Is there a way to enforce rebase+squash vs. merge on the PR, >> since, per Allen, Yetus requires one commit to work? > > > I don’t know about the J

Re: Github integration for Hadoop

> > > > 2) Better attribution of contributors with their GH id (Arpit) > > > > This doesn't happen very naturally other than the pull requests are > typically shown in their fork of the apache repo. > > It happens if we used PRs for integration, but yes I agree that it does not if GH is just used a

Re: Github integration for Hadoop

> * Have we tried our precommit on PRs yet? Does it work for multiple > branches? Is there a way to enforce rebase+squash vs. merge on the PR, > since, per Allen, Yetus requires one commit to work? I don’t know about the Jenkins-side of things (e.g., how does Jenkins trigger a build?).

Re: Github integration for Hadoop

> > > >> > >> > If that's the case, we should also look at review alternatives > >> > like RB and Crucible. > >> > >> Okay by me if the community consensus supports one of them. The fact > that > >> they exist but no one uses them is not a ringing endorsement. > >> > >> HBase uses reviewboard, as d

Re: FYI: Major, long-standing Issue with trunk's test-patch

Thanks for finding this issue, Allen. This is somewhat of a tangent, but I'm curious who still uses hadoop-pipes. Certainly development has more or less stopped on it. I think the last 5 years of commits on it have been things like updating version numbers, fixing missing #includes, moving to CMa

Re: Github integration for Hadoop

On Fri, Oct 30, 2015 at 10:20 AM, Andrew Wang wrote: > I'm trying to slow this discussion down so we can: > > a) Determine the problem(s) we're trying to solve > The problem is that many people like the github code review tools. Enabling the github integration does not mean that everyone has to

[jira] [Created] (HADOOP-12533) Introduce FileNotFoundException in WASB for read and seek API

Dushyanth created HADOOP-12533: -- Summary: Introduce FileNotFoundException in WASB for read and seek API Key: HADOOP-12533 URL: https://issues.apache.org/jira/browse/HADOOP-12533 Project: Hadoop Common

[GitHub] hadoop pull request: HADOOP-11919 Testing Github integration

Github user asfgit closed the pull request at: https://github.com/apache/hadoop/pull/40 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

Re: Github integration for Hadoop

I'm trying to slow this discussion down so we can: a) Determine the problem(s) we're trying to solve b) See how the proposed solutions meet this problem The flood of +1's were made before a full proposal of what "enabling github integration" means, which has only been really specified in Owen's m

Re: building branch-2 on windows

How do other branches fare in that regard (I don't have easy access to a windows machine atm)? On Fri, Oct 30, 2015 at 7:20 AM, Steve Loughran wrote: > > On 28 Oct 2015, at 21:28, Chris Nauroth cnaur...@hortonworks.com>> wrote: > > I just confirmed that I can build the release-2.6.2-RC0 tag fro

Re: [GitHub] hadoop pull request: HADOOP-11919 Testing Github integration

Responding to a comment on github. On Fri, Oct 30, 2015 at 10:11 AM, omalley wrote: > Github user omalley commented on the pull request: > > https://github.com/apache/hadoop/pull/40#issuecomment-152589471 > > Testing comments on github pull requests. > > > --- > If your project is set up

Re: Github integration for Hadoop

I think we should take more than 24 hours of discussion to make a big, fundamental change to our code review process. I used github while working on the Spark project, and frankly I didn't like it. I didn't like the way it split the discussion between JIRA and github. Also, often people would fi

[GitHub] hadoop pull request: HADOOP-11919 Testing Github integration

GitHub user omalley opened a pull request: https://github.com/apache/hadoop/pull/40 HADOOP-11919 Testing Github integration This is a test. You can merge this pull request into a Git repository by running: $ git pull https://github.com/omalley/hadoop hadoop-11919 Alternatively

[GitHub] hadoop pull request: HADOOP-11919 Testing Github integration

Github user omalley commented on the pull request: https://github.com/apache/hadoop/pull/40#issuecomment-152589471 Testing comments on github pull requests. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project

[jira] [Created] (HADOOP-12532) Data race in IPC client Client.stop()

Wei-Chiu Chuang created HADOOP-12532: Summary: Data race in IPC client Client.stop() Key: HADOOP-12532 URL: https://issues.apache.org/jira/browse/HADOOP-12532 Project: Hadoop Common Issue

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

See Changes: [jlowe] MAPREDUCE-6528. Memory leak for HistoryFileManager.getJobSummary(). -- [...truncated 6148 lines...] Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPer

Jenkins build is back to normal : Hadoop-Common-trunk #1929

See

Re: Github integration for Hadoop

It seems like there is overwhelming support for enabling the github integration, so I went ahead and filed the infra ticket . This is explicitly not changing the way that we commit on Hadoop and commits should be squashed an

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

See Changes: [kihwal] HDFS-4937. ReplicationMonitor can infinite-loop in [kihwal] fix CHANGES.txt [jlowe] Creating 2.6.3 entries in CHANGES.txt files. [jlowe] Update CHANGES.txt to reflect commit of MR-6273 to branch-2.6 --

Re: Java 8 + Jersey updates

On Fri, Oct 30, 2015 at 11:16 PM, Steve Loughran wrote: > >> On 29 Oct 2015, at 15:40, Tsuyoshi Ozawa wrote: >> >> Steve, >> >>> If you exclude jax-rs 2 and try to stay @ jersey 1.9 for your client, all >>> the http clients: KMS, webhdfs, ATS, aren't going to link. >> >> I thought we can use Jer

Re: building branch-2 on windows

On 28 Oct 2015, at 21:28, Chris Nauroth mailto:cnaur...@hortonworks.com>> wrote: I just confirmed that I can build the release-2.6.2-RC0 tag from source on Windows, including the native components. For zlib, my setup is to have the source extracted in C:\zlib-1.2.7, and that's where I point ZLI

Re: Java 8 + Jersey updates

> On 29 Oct 2015, at 15:40, Tsuyoshi Ozawa wrote: > > Steve, > >> If you exclude jax-rs 2 and try to stay @ jersey 1.9 for your client, all >> the http clients: KMS, webhdfs, ATS, aren't going to link. > > I thought we can use Jersey 1.19 on JDK 8 with client-side > compatibility, but do you

[jira] [Created] (HADOOP-12531) Regroup of all Hadoop Ecosystem UIs

SERGENT David created HADOOP-12531: -- Summary: Regroup of all Hadoop Ecosystem UIs Key: HADOOP-12531 URL: https://issues.apache.org/jira/browse/HADOOP-12531 Project: Hadoop Common Issue Type:

[jira] [Resolved] (HADOOP-12530) Error when trying to format HDFS by running hdfs namenode -format

[ https://issues.apache.org/jira/browse/HADOOP-12530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton resolved HADOOP-12530. --- Resolution: Not A Problem Assignee: Daniel Templeton This is a configuration i

[jira] [Created] (HADOOP-12530) Error when trying to format HDFS by running hdfs namenode -format

Nadia created HADOOP-12530: -- Summary: Error when trying to format HDFS by running hdfs namenode -format Key: HADOOP-12530 URL: https://issues.apache.org/jira/browse/HADOOP-12530 Project: Hadoop Common

Jenkins build is back to normal : Hadoop-common-trunk-Java8 #626

See

Build failed in Jenkins: Hadoop-Common-trunk #1928

See Changes: [ozawa] Add an entry of YARN-4312 to CHANGES.txt [ozawa] YARN-4320. TestJobHistoryEventHandler fails as AHS in MiniYarnCluster no -- [...truncated 5420 lines...] Running org.apa

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

See Changes: [ozawa] Move YARN-3580 in CHANGES.txt from 2.8 to 2.7.2. [szetszwo] HDFS-9323. Randomize the DFSStripedOutputStreamWithFailure tests. -- [...truncated 3907 lines...] --

Build failed in Jenkins: Hadoop-Common-trunk #1927

See Changes: [ozawa] Move YARN-3580 in CHANGES.txt from 2.8 to 2.7.2. [szetszwo] HDFS-9323. Randomize the DFSStripedOutputStreamWithFailure tests. -- [...truncated 4143 lines...] Loading sou

Re: Github integration for Hadoop

+1 if the current review process is kept. Pros: * Using PRs is good for increasing developers because PRs are very familiar for many developers. * Better UI. (no need to copy the diff manually for reviewing patches!) Cons: * Discussions can be split. However, according to the below blog post

Re: Github integration for Hadoop

Andrew, look at Spark github. They use PRs and I do not see extra merge commits. Committer can do fast-farward merge using git command line. PRs are used to leave inline feedbacks for the fix On Oct 29, 2015 1:34 PM, "Andrew Wang" wrote: > Has anything changed regarding the github integration sin