Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 4E125200C2C for ; Fri, 17 Feb 2017 05:07:49 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 4CAD7160B6F; Fri, 17 Feb 2017 04:07:49 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 6E62E160B61 for ; Fri, 17 Feb 2017 05:07:48 +0100 (CET) Received: (qmail 55345 invoked by uid 500); 17 Feb 2017 04:07:47 -0000 Mailing-List: contact dev-help@reef.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@reef.apache.org Delivered-To: mailing list dev@reef.apache.org Received: (qmail 55333 invoked by uid 99); 17 Feb 2017 04:07:47 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Feb 2017 04:07:47 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id CCEE2C1446 for ; Fri, 17 Feb 2017 04:07:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.552 X-Spam-Level: X-Spam-Status: No, score=-0.552 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id dxt4seiUfAdK for ; Fri, 17 Feb 2017 04:07:45 +0000 (UTC) Received: from mail-pf0-f175.google.com (mail-pf0-f175.google.com [209.85.192.175]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 5E0175FB89 for ; Fri, 17 Feb 2017 04:07:44 +0000 (UTC) Received: by mail-pf0-f175.google.com with SMTP id 189so10463719pfu.3 for ; Thu, 16 Feb 2017 20:07:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:date:subject:message-id :references:in-reply-to:to; bh=8i2ewOtMhdJ0DWoq70rGN39hj733BTypNJVjHBOaTtk=; b=uy82vCyhlXFrNE65+Z6rlvWeq6kMGD4o4nwcMGp8XIwELBtaJ/z7Hpk6gGblt2EvGA OtgJVkPpCRxEgMaS5c++oE/LJq7EIKvHDyFdZbZ9c6rGGOtoB9b+fcqaaP96PfZva8mS 2ABNF81eBkelqwDOL/1aUKwbbh7zQqigLZqBglC642wNIWRju7/D2L5ZOw6gC4NMYKWm yZvFUiWl7inqclwni3tQDPYXX/2cZRlvaNJ0s12Ysdp6qLopcJTNeXYpoc9VvGV/q5yX 7tgvi5murbTQcjvbCZA1Psr1vSEY6vG/oF6NirUW55MwNTgeXbPS5UxYKiepztVCHr3t 2xAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version:date :subject:message-id:references:in-reply-to:to; bh=8i2ewOtMhdJ0DWoq70rGN39hj733BTypNJVjHBOaTtk=; b=RxZT1ts1GpkUL1PYYPQJj8i7xZRtp/co8CxnlaRSn+PCVkc1FbDmAF8/yjBY31/Xq0 +aaowO5jvWWbuZyEjKkrdnpZm3apu1ekFv5vUxS+tFIj/Xtq0NMqbFXh2fp1sUV1WuOf 3Q+lV4T4qZ2VcAnzBx40igtpi+/YMEwp9YJy3Y8XRo0MhROGSY6SxHBQiLIAN0qt4oJ0 xavNV0t5sVI8LhruC2RzBLa6/3URVMiWvb5oGffBUliZ7LxvJouj67CX+tsGdU9DJhKc UtH2QPR9ViQWsPqGLzBIdCLSil5Tdzmrhrf1OAMoGGf4L2KMXs6bhA0/6KvzxCEBsJ3o n7MQ== X-Gm-Message-State: AMke39kRrZY2pMWeE51GfFzfZiTVeOckKmlXnsVROZh1yp5uovxLYj8ojb7ENZe9K2Xfew== X-Received: by 10.99.8.70 with SMTP id 67mr7275862pgi.205.1487304462761; Thu, 16 Feb 2017 20:07:42 -0800 (PST) Received: from [192.168.1.13] (c-24-18-189-85.hsd1.wa.comcast.net. [24.18.189.85]) by smtp.gmail.com with ESMTPSA id o18sm5483768pgn.36.2017.02.16.20.07.41 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Feb 2017 20:07:42 -0800 (PST) From: Saikat Kanjilal Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Thu, 16 Feb 2017 20:07:40 -0800 Subject: Re: 0.16? Message-Id: <936B6E93-C753-4917-9CAC-A81910BC9948@gmail.com> References: <91579B44-6C9C-4FA9-8DB3-4FEF0C0D5DC3@gmail.com> <4B2CA4CF-7891-4D66-B07F-D1CF4D2EC6D5@gmail.com> In-Reply-To: To: dev@reef.apache.org X-Mailer: iPad Mail (14D27) archived-at: Fri, 17 Feb 2017 04:07:49 -0000 Sergei, I definitely have more experience with Java than .Net, maybe this is a JIRA t= hat I also add to my collection and help you, might be a good case for pair c= oding as well, let me know how you want to move forward. Thanks Sent from my iPad > On Feb 16, 2017, at 6:23 PM, Sergiy Matusevych wrote: >=20 > Hi Saikat, >=20 > The cleanup work is purely Java, so if you are working on the .NET side of= > things, I don't see much sense to switch the environment just for these > issues. Still, it would be nice to get some help - maybe there are > volunteers willing to debug some race conditions in Java and on YARN? >=20 > Thank you, > Sergiy. >=20 >> On Thu, Feb 16, 2017 at 6:11 PM, Saikat Kanjilal wrot= e: >>=20 >> Me and my big mouth :))))), just kidding, I am already working on .Net >> core 2.0 conversion JIRA's , what sort of dev/test help can I provide? >>=20 >> Sent from my iPhone >>=20 >>> On Feb 16, 2017, at 5:41 PM, Sergiy Matusevych < >> sergiy.matusevych@gmail.com> wrote: >>>=20 >>> Hi Saikat, >>>=20 >>> The failures are sporadic and most likely are due to some race condition= s >>> during the cleanup process. You don't need CI to replicate them, but we >>> need to debug the issues not only in local mode, but also on YARN (and, >>> ideally, for all other runtimes that we provide). A good indicator of >>> successful cleanup would be JIRA issue >>> https://issues.apache.org/jira/browse/REEF-1715 - when all threads are >>> closed properly, we would no longer need System.exit() call at the end o= f >>> the Driver or Evaluator processes (regardless of the runtime). Would you= >> be >>> interested in helping me with that part? >>>=20 >>> Thank you, >>> Sergiy. >>>=20 >>>=20 >>>> On Thu, Feb 16, 2017 at 5:29 PM, Saikat Kanjilal >> wrote: >>>>=20 >>>> Out of curiosity have we been able to replicate these failures locally ,= >>>> am wondering whether there's a need to have a local version of Travis c= i >>>> setup? >>>>=20 >>>> Sent from my iPhone >>>>=20 >>>>> On Feb 16, 2017, at 5:22 PM, Boris Shulman wrote:= >>>>>=20 >>>>> Is AM HA part of 0.16? >>>>>=20 >>>>> Sent from my iPhone >>>>>=20 >>>>>> On Feb 16, 2017, at 12:22 PM, Sergiy Matusevych < >>>> sergiy.matusevych@gmail.com> wrote: >>>>>>=20 >>>>>> Hi Markus, >>>>>>=20 >>>>>> I think we can safely announce that Unmanaged AM and REEF-on-REEF wil= l >>>> be >>>>>> part of 0.16, but the bugs that Mariia mentions prevent us from >> calling >>>>>> this release REEF-as-a-Library. Even for the unmanaged AM, I need som= e >>>> time >>>>>> (likely till the end of this sprint) to make sure that Unmanaged AM >>>> works >>>>>> properly on Hadoop 2.7.3 and above. >>>>>>=20 >>>>>> Thanks, >>>>>> Sergiy. >>>>>>=20 >>>>>> On Thu, Feb 16, 2017 at 9:43 AM, Mariia Mykhailova < >>>>>> mamykhai@microsoft.com.invalid> wrote: >>>>>>=20 >>>>>>> There are several transient test failures in both Java and .NET test= s >>>> and >>>>>>> Travis CI job timeout (which indicates hidden problems in terminatin= g >>>> Java >>>>>>> REEF jobs) which we've introduced since 0.15. I don't think we shoul= d >>>> do a >>>>>>> release with these issues uninvestigated, especially Travis timeout.= >>>> For >>>>>>> now I've marked them as blocking REEF-1444. >>>>>>>=20 >>>>>>> -Mariia >>>>>>>=20 >>>>>>>=20 >>>>>>> ________________________________ >>>>>>> From: Markus Weimer >>>>>>> Sent: Thursday, February 16, 2017 9:31:35 AM >>>>>>> To: REEF Developers Mailinglist >>>>>>> Subject: 0.16? >>>>>>>=20 >>>>>>> Hi, >>>>>>>=20 >>>>>>> where are we in the process of releasing 0.16? In other words: If we= >>>> called >>>>>>> the release today, what amazing feature that is on the cusp of >> getting >>>> in >>>>>>> would we loose? >>>>>>>=20 >>>>>>> I'm not suggesting to literally do it today, but a release around th= e >>>> VS >>>>>>> 2017 availability would be convenient for us to switch to the new >> build >>>>>>> system and all early in the works towards 0.17. >>>>>>>=20 >>>>>>> Markus >>>>>>>=20 >>>>=20 >>=20