Return-Path: X-Original-To: apmail-ignite-dev-archive@minotaur.apache.org Delivered-To: apmail-ignite-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3D592188A0 for ; Mon, 16 Nov 2015 12:02:24 +0000 (UTC) Received: (qmail 24985 invoked by uid 500); 16 Nov 2015 12:02:24 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 24942 invoked by uid 500); 16 Nov 2015 12:02:23 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 24930 invoked by uid 99); 16 Nov 2015 12:02:23 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Nov 2015 12:02:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 307D1C56FD for ; Mon, 16 Nov 2015 12:02:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.9 X-Spam-Level: ** X-Spam-Status: No, score=2.9 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id ni0fKhNPw_Ad for ; Mon, 16 Nov 2015 12:02:13 +0000 (UTC) Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 6528C20B90 for ; Mon, 16 Nov 2015 12:02:12 +0000 (UTC) Received: by wmec201 with SMTP id c201so116282752wme.1 for ; Mon, 16 Nov 2015 04:02:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=pkH5wfao8Eyn2Jd1cxyHyhvdrQ2wiPuwUNbyhbNOe4U=; b=puJHN1wabV9f3N2t3nbwKSeGz6zMQKYr1YgU+MPXfiu6xdBIA67JAhxp2/HtJKrBB7 K4EB/xTP8nR9SlRwxhhKE7LvuvutoVhm+z1cyXJIL+ahbw9RqHq2NcIdF1SF5Em/M+kn wXBTb0BvCWG5EZ2389CzkYoG4jpfQfUyMZpu/xskAhzK7eXfepFAcIHGeu1mD3T/3Zkr jQLk1/AxeNgycUOnz3cv+zxd/OspkYzoQX1uTLLzZLXYnrIR7xjH/bAj4tbw0hGd3RGE HnJQiCs2SeNCEKstMzP1Pja7/IN/afTGTDE5C5YxB2QkaQvg4XBimxRMq6cavOnQlWwm T8XQ== MIME-Version: 1.0 X-Received: by 10.28.93.145 with SMTP id r139mr17500351wmb.20.1447675332014; Mon, 16 Nov 2015 04:02:12 -0800 (PST) Received: by 10.194.243.100 with HTTP; Mon, 16 Nov 2015 04:02:11 -0800 (PST) In-Reply-To: References: <5645D847.7060405@gridgain.com> <6D2F12AB-6E90-4102-BF8B-F185BA3FC337@gridgain.com> Date: Mon, 16 Nov 2015 15:02:11 +0300 Message-ID: Subject: Re: IGNITE-1227 patch available From: Amir Akhmedov To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary=001a1145ace4ea37300524a72d87 --001a1145ace4ea37300524a72d87 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Denis, Artem, Thank you guys for clarification. Latter I'll provide a pull-request for this ticket. I think the page [1] should also be updated, cause I followed the steps from there. [1] https://ignite.apache.org/community/contribute.html#contribute 2015-11-16 14:26 GMT+03:00 Artem Shutak : > Denis, Amir, > > First of all, need to understand how it works on TC. TC downloads a patch > file and applies it by 'git am ' to the latest master. That i= s > mentioned on How to Contribute > - > see "2. Create a Patch-file"/"Applying" > > As I see in build logs ( > > http://ci.ignite.apache.org/viewLog.html?buildId=3D75417&buildTypeId=3DIg= nite_IgniteCacheFullApi&tab=3DbuildLog&state=3D&expand=3Dnone#_state=3D78&f= ocus=3D78 > ) > the patch-file couldn't be applied. > > Step 3/7: Apply patch (if exist) (Gradle) > ... > :patchapply > ... > [10:32:08]Trying to apply patch. > [10:32:08]Executing command 'git am > dev-tools/IGNITE-1227-12772149.patch'... > [10:32:08]Command output: > [10:32:08] > [10:32:08]Return code: 1 > [10:32:08]Patch was not applied successfully. Aborting patch applying. > > I did it locally and got "Patch format detection failed.". According to a > head of the content of the file, the patch has been created by IDEA - it'= s > wrong way. To create patch manually you need to use "git format-patch" or= I > recommend you to use "/scripts/git-format-patch.sh". See How > to Contribute > - > "2. > Create a Patch-file". > > Also, I want to say +1 for an Denis's advice to use a pull-request way. > This way has no minuses and has a lots of pluses by my opinion against > patch-way. > > Thanks, > -- Artem -- > > On Mon, Nov 16, 2015 at 1:39 PM, Denis Magda wrote: > > > Amir, before making a review I want to be sure that all Ignite test > suites > > are green. > > > > However, seems that the patch based way contribution is broken. When I > > open a test run info for any suite I see the following > > http://ci.ignite.apache.org/viewLog.html?buildId=3D75417 > > > > FAILURE: Build failed with an exception. > > > > * What went wrong: > > Execution failed for task ':patchapply'. > > > Process 'command '/usr/lib/jvm/java-7-oracle/bin/java'' finished with > > non-zero exit value 1 > > > > > > Artem, do we still support the patch based contribution? > > > > Amir, until we=E2=80=99re resolving issue with the patches please follo= w the > > pull-request way. This way of contribution is a preferred one and works > > fine: > > > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#Howt= oContribute-1.CreateGitHubpull-request > > < > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#Howt= oContribute-1.CreateGitHubpull-request > > > > > Before you push your pull request please get to know our coding > guidelines > > (identations, brackets usage, etc.). You have some issues in your code > > related to guidelines. You=E2=80=99ll see them when familiarize yoursel= f with > this > > doc: > > https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines < > > https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines> > > > > > > Regards, > > Denis > > > > > On 13 =D0=BD=D0=BE=D1=8F=D0=B1. 2015 =D0=B3., at 15:32, Denis Magda <= dmagda@gridgain.com> > wrote: > > > > > > Amir, great thanks! > > > > > > If you don't mind I'll review your changes in a couple of days. > > > > > > > > > However, probably someone else will do this earlier:) > > > > > > -- > > > Denis > > > > > > > > > From: Amir Akhmedov > amir.akhmedov@gmail.com>> > > > Date: Fri, Nov 13, 2015 at 11:28 AM > > > Subject: IGNITE-1227 patch available > > > To: dev@ignite.apache.org > > > > > > > > > Hi Igniters, > > > > > > I submitted patch for IGNITE-1227 > > > > https://issues.apache.org/jira/browse/IGNITE-1227>>, could review it > > > whenever it is possible. > > > > > > Thanks. > > > > > > -- > > > Sincerely Yours Amir Akhmedov > > > > > > > > > > > --=20 Sincerely Yours Amir Akhmedov --001a1145ace4ea37300524a72d87--