Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-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 78E0410C83 for ; Wed, 11 Dec 2013 23:24:22 +0000 (UTC) Received: (qmail 77094 invoked by uid 500); 11 Dec 2013 23:24:22 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 77076 invoked by uid 500); 11 Dec 2013 23:24:22 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 77061 invoked by uid 99); 11 Dec 2013 23:24:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Dec 2013 23:24:22 +0000 Date: Wed, 11 Dec 2013 23:24:22 +0000 (UTC) From: "Myrna van Lunteren (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DERBY-5865) On IBM 1.7 TestDurabilityProperty fails with FAIL -- derby.system.durability=test mode seems to be broken. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845840#comment-13845840 ] Myrna van Lunteren commented on DERBY-5865: ------------------------------------------- I don't think this timing part of the test is ever going to be stable. Any objections to just taking it out? Any suggestions for testing sync to disk another way? > On IBM 1.7 TestDurabilityProperty fails with FAIL -- derby.system.durability=test mode seems to be broken. > ----------------------------------------------------------------------------------------------------------- > > Key: DERBY-5865 > URL: https://issues.apache.org/jira/browse/DERBY-5865 > Project: Derby > Issue Type: Bug > Components: Store > Affects Versions: 10.10.1.1 > Environment: Linux trunk version: 10.10.0.0 alpha - (1362738) > Reporter: Kathey Marsden > Assignee: Kathey Marsden > Labels: derby_triage10_10 > > I saw this failure on IBM 1.7 on 7/17/2012 > http://people.apache.org/~myrnavl/derby_test_results/main/linux/testlog/ibm17/1362738-derbyall_diff.txt > ********* Diff file derbyall/storeall/storemore/TestDurabilityProperty.diff > *** Start: TestDurabilityProperty jdk1.7.0 storeall:storemore 2012-07-18 01:45:06 *** > 1a2,5 > > FAIL -- derby.system.durability=test mode seems to be broken. > > -- In this mode one would expect that inserts with autocommit off and on would be in the same range as syncs are not happening but the difference here seems to be more than the approximate estimated range. > > -- Also comparing the time taken to do the inserts without this property set seems to be in the same range as with this property set. > > -- Please note this test times inserts and approximate estimates were considered to report this observation. > Test Failed. > *** End: TestDurabilityProperty jdk1.7.0 storeall:storemore 2012-07-18 01:46:39 *** -- This message was sent by Atlassian JIRA (v6.1.4#6159)