Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0C052C727 for ; Fri, 8 Jun 2012 03:16:08 +0000 (UTC) Received: (qmail 35901 invoked by uid 500); 8 Jun 2012 03:16:06 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 35782 invoked by uid 500); 8 Jun 2012 03:16:06 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 35728 invoked by uid 99); 8 Jun 2012 03:16:04 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jun 2012 03:16:04 +0000 Received: from localhost (HELO mail-ob0-f176.google.com) (127.0.0.1) (smtp-auth username cdouglas, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jun 2012 03:16:04 +0000 Received: by obbef5 with SMTP id ef5so2459575obb.35 for ; Thu, 07 Jun 2012 20:16:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.60.20.197 with SMTP id p5mr3419765oee.32.1339125363711; Thu, 07 Jun 2012 20:16:03 -0700 (PDT) Received: by 10.182.154.1 with HTTP; Thu, 7 Jun 2012 20:16:03 -0700 (PDT) In-Reply-To: References: <4FD10B4F.7020406@syncsort.com> Date: Thu, 7 Jun 2012 20:16:03 -0700 Message-ID: Subject: Re: Randomly failing test From: Chris Douglas To: common-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable It would be surprising if the test became flakier with those modifications if the changes did not also change the semantics. From the test output, the patch is causing an assertion to fail: more records are hitting disk than expected. -C On Thu, Jun 7, 2012 at 7:07 PM, Asokan, M wrote: > Hi Chris, > =A0 Thanks for your reply. =A0I submitted a patch for MAPREDUCE-2454. =A0= I got this failing test error and I am blocked on this. =A0Can you please a= dvise me how I proceed submitting the patch? =A0I can spend some time inves= tigating how to make the test more deterministic if that is possible(either= tuning some of the parameters or increasing child JVM memory?) > > Thanks > -- Asokan > ________________________________________ > From: Chris Douglas [cdouglas@apache.org] > Sent: Thursday, June 07, 2012 9:02 PM > To: common-dev@hadoop.apache.org > Subject: Re: Randomly failing test > > The output on MAPREDUCE-4094 is no longer available, but a failed job > during an integration test could be traced to nondeterminism anywhere > in that chain. The "flakiness" you observe is common to many Hadoop > integration tests. > > The purpose of the test is to verify that 1) the merge works when some > segments are retained in memory during the reduce 2) the tuning > parameters for the reduce have the expected effect. -C > > On Thu, Jun 7, 2012 at 1:13 PM, Asokan, M wrote: >> Can someone guide me in making the test org.apache.hadoop.mapred.TestRed= uceFetchFromPartialMem less flaky? =A0I see test failures mentioned in MAPR= EDUCE-4094 and MAPREDUCE-4096 but no fix is available so far. >> >> Thanks. >> >> -- Asokan >> >> >> ________________________________ > > > > ATTENTION: ----- > > The information contained in this message (including any files transmitte= d with this message) may contain proprietary, trade secret or other =A0conf= idential and/or legally privileged information. Any pricing information con= tained in this message or in any files transmitted with this message is alw= ays confidential and cannot be shared with any third parties without prior = written approval from Syncsort. This message is intended to be read only by= the individual or entity to whom it is addressed or by their designee. If = the reader of this message is not the intended recipient, you are on notice= that any use, disclosure, copying or distribution of this message, in any = form, is strictly prohibited. If you have received this message in error, p= lease immediately notify the sender and/or Syncsort and destroy all copies = of this message in your possession, custody or control.