Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1487951904.1259898860736.JavaMail.jira@brutus>
Date: Fri, 4 Dec 2009 03:54:20 +0000 (UTC)
From: "Bryan Pendleton (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4297) 'compilation time did not compute
 (0,0,0,0) expected:<16> but was:<0>' in
 testGroupBySortProps(....tests.lang.XplainStatisticsTest)
In-Reply-To: <712911361.1246624127173.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785735#action_12785735 ] 

Bryan Pendleton commented on DERBY-4297:
----------------------------------------

Hi Ole, I just noticed this, sorry I didn't pay attention to it before.

Does this happen routinely? Or did it happen only once?

The values "16" and "0" are interesting because on Windows,
System.currentTimeMillis returns values from the 60 Hz timer
which means that the values often appear to advance in "jumps"
of 16 (sometimes 15).

This might be a problem in the test, which is a relatively new test,
or it might indicate a weakness in the compile_time measurement
logic in the compilation code.

> 'compilation time did not compute (0,0,0,0) expected:<16> but was:<0>' in testGroupBySortProps(....tests.lang.XplainStatisticsTest)
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4297
>                 URL: https://issues.apache.org/jira/browse/DERBY-4297
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL, Test
>    Affects Versions: 10.6.0.0
>         Environment: OS:
> Microsoft Windows XP Professional - 5.1.2600 Service Pack 3 Build 2600
> CYGWIN_NT-5.1 1.5.25(0.156/4/2) 2008-06-12 19:34 Cygwin
> JVM:
> Sun Microsystems Inc.
> java version "1.5.0_16"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b02)
> Java HotSpot(TM) Client VM (build 1.5.0_16-b02, mixed mode, sharing)
>            Reporter: Ole Solberg
>            Priority: Minor
>
> Seen in
> http://dbtg.thresher.com/derby/test/trunk15/jvm1.5/testing/testlog/CYGWIN_NT-5.1_i686-unknown/790694-org.apache.derbyTesting.functionTests.suites.All_diff.txt
> There was 1 failure:
> 1) testGroupBySortProps(org.apache.derbyTesting.functionTests.tests.lang.XplainStatisticsTest)junit.framework.AssertionFailedError: compilation time did not compute (0,0,0,0) expected:<16> but was:<0>
> 	at org.apache.derbyTesting.functionTests.tests.lang.XplainStatisticsTest.verifySensibleStatementTimings(XplainStatisticsTest.java:707)
> 	at org.apache.derbyTesting.functionTests.tests.lang.XplainStatisticsTest.testGroupBySortProps(XplainStatisticsTest.java:1011)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:109)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.