Return-Path: X-Original-To: apmail-geode-issues-archive@minotaur.apache.org Delivered-To: apmail-geode-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0E9B61831E for ; Fri, 23 Oct 2015 19:55:31 +0000 (UTC) Received: (qmail 78787 invoked by uid 500); 23 Oct 2015 19:55:30 -0000 Delivered-To: apmail-geode-issues-archive@geode.apache.org Received: (qmail 78755 invoked by uid 500); 23 Oct 2015 19:55:30 -0000 Mailing-List: contact issues-help@geode.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.incubator.apache.org Delivered-To: mailing list issues@geode.incubator.apache.org Received: (qmail 78746 invoked by uid 99); 23 Oct 2015 19:55:30 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Oct 2015 19:55:30 +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 75A37C082C for ; Fri, 23 Oct 2015 19:55:30 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.97 X-Spam-Level: X-Spam-Status: No, score=0.97 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id ZoRdopcE07pN for ; Fri, 23 Oct 2015 19:55:29 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with SMTP id D860E27DB4 for ; Fri, 23 Oct 2015 19:55:28 +0000 (UTC) Received: (qmail 78735 invoked by uid 99); 23 Oct 2015 19:55:28 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Oct 2015 19:55:28 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id C75A92C1F65 for ; Fri, 23 Oct 2015 19:55:27 +0000 (UTC) Date: Fri, 23 Oct 2015 19:55:27 +0000 (UTC) From: "Jason Huynh (JIRA)" To: issues@geode.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (GEODE-486) ConcurrentIndexUpdateWithWLDUnitTest needs to be rewritten/cleaned up MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jason Huynh created GEODE-486: --------------------------------- Summary: ConcurrentIndexUpdateWithWLDUnitTest needs to be rewritten/cleaned up Key: GEODE-486 URL: https://issues.apache.org/jira/browse/GEODE-486 Project: Geode Issue Type: Improvement Components: tests Reporter: Jason Huynh This test has misleading variables such as parameters being passed in as 30*000 (which obviously is 0 but this is supposed to be a parameter for join wait time, which means it waits infinitely and not that it doesn't wait at all) This test along with any other test that uses PRQueryDUnitHelper should be written to not use the randomOps runnable. Due to the nature of the test, the test exhausts different scenarios based on randomness and can fail/pass intermittently and fail for possibly different reasons. Perhaps we can write a test to test the various scenarios we are hoping to exhaust with these random operations. Such as test multiple puts on same keys for a specific index and make sure the index is maintained correctly. Another test could be test multiple puts on different keys etc. We may be able to have an overarching test that does these random operations but I don't think we should have a lot of these it's almost like writing the same test multiple times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)