db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5208) largeDataTests run but give no result
Date Fri, 01 Jul 2011 12:44:28 GMT

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

Kathey Marsden updated DERBY-5208:

    Attachment: results_trunk_1141176.zip

Attaching the results for the test run on trunk on linux. (Note the version shows M but it
is just a small change to another test not related to this one).
The test passed for embedded in 10 hours 14 minutes:
*** Start: LobLimits jdk1.7.0 largeData:largeDataTests 2011-06-30 15:19:11 ***
*** End:   LobLimits jdk1.7.0 largeData:largeDataTests 2011-07-01 01:33:04 ***

It was excluded for client with the comment:
# excluding largedata/LobLimits.java to run with the network server because curr
ently lobs are materialized and this test tests for 2G lobs.
#                       see DERBY-326 and DERBY-550 issues

I'll open another issue to investigate if this test can be run for client now that these issues
are fixed.

> 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:,,,,
>            Reporter: Myrna van Lunteren
>            Assignee: Kathey Marsden
>         Attachments: results_trunk_1141176.zip
> 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 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 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; 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


View raw message