Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 1 Jul 2011 12:30:28 +0000 (UTC)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <154603647.8495.1309523428759.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <594367181.9404.1304012643127.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (DERBY-5208) largeDataTests run but give no
 result
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden reassigned DERBY-5208:
-------------------------------------

    Assignee: Kathey Marsden

Assigning to myself to investigate.  This issue was discussed on the list in this thread:
http://old.nabble.com/Largedata-test-history-ts31963968.html


> largeDataTests run but give no result
> -------------------------------------
>
>                 Key: DERBY-5208
>                 URL: https://issues.apache.org/jira/browse/DERBY-5208
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.3.3.1, 10.5.3.2, 10.7.1.1, 10.8.1.2, 10.9.0.0
>            Reporter: Myrna van Lunteren
>            Assignee: Kathey Marsden
>
> In my nightly processes the largeDataTests suite runs and sometimes finishes, but even if it finishes, the _fail.txt, _diff.txt _skip.txt *and* _pass.txt file are all empty. I kicked off a manual run for the 10.8.1.2 RC and here too the result files were empty, except for _report, which shows nothing ran, although there was definitely a test process busy for many hours. (and _props, which is irrelevant).
> I ran this for the 10.7.1.1 release by hand (on 2011-02-28) and it was successful that time, but I've noticed this behavior on more than one branch in the nightlies, so I don't think it's a regression per se for 10.8.1.2; 10.7.1.1. was with a slightly different jvm version ( java.fullversion=JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr9-20101124_69295
> (JIT enabled, AOT enabled) vs.  java.fullversion=JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr9-20110203_74623
> (JIT enabled, AOT enabled)), perhaps that's related.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira