Derby
  1. Derby
  2. DERBY-5208

largeDataTests run but give no result

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Not a Problem
    • Affects Version/s: 10.3.3.1, 10.5.3.2, 10.7.1.1, 10.8.1.2, 10.9.1.0
    • Fix Version/s: None
    • Component/s: Test
    • Labels:
      None
    • Bug behavior facts:
      Regression Test Failure

      Description

      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.

        Activity

        Hide
        Knut Anders Hatlen added a comment -

        [bulk update] Close all resolved issues that haven't been updated for more than one year.

        Show
        Knut Anders Hatlen added a comment - [bulk update] Close all resolved issues that haven't been updated for more than one year.
        Hide
        Kathey Marsden added a comment -

        Closing not a problem as It looks like this is just a matter of the test not having enough time to finish, so not an issue with Derby itself but the run in question. The test has now been converted to JUnit largedata.LobLimitsTest DERBY-1903. Maybe this will make the test easier to run concurrently so it does not run out of time.

        Show
        Kathey Marsden added a comment - Closing not a problem as It looks like this is just a matter of the test not having enough time to finish, so not an issue with Derby itself but the run in question. The test has now been converted to JUnit largedata.LobLimitsTest DERBY-1903 . Maybe this will make the test easier to run concurrently so it does not run out of time.
        Hide
        Kathey Marsden added a comment -

        I ran with an insane build on the latest on 10.3, 10.5 and trunk on my RHEL inux machine with the following results:
        10.3.3.1 - (1140949) - 10 hours 52 minutes
        10.5.3.2 - (1140944) - 10 hours 12 minutes
        trunk 10.9.0.0 alpha - (1141774) - 10 hours 18 minutes

        So it looks like we have have not had any major deterioration in the test performance and some improvement from 10.3 to 10.5. I was surprised that my insane run was no faster than the sane one.

        Show
        Kathey Marsden added a comment - I ran with an insane build on the latest on 10.3, 10.5 and trunk on my RHEL inux machine with the following results: 10.3.3.1 - (1140949) - 10 hours 52 minutes 10.5.3.2 - (1140944) - 10 hours 12 minutes trunk 10.9.0.0 alpha - (1141774) - 10 hours 18 minutes So it looks like we have have not had any major deterioration in the test performance and some improvement from 10.3 to 10.5. I was surprised that my insane run was no faster than the sane one.
        Hide
        Kathey Marsden added a comment -

        I opened DERBY-5308 for the client issue. Also I realized I should have been running with an insane build. Previous results were for a sane build.

        Show
        Kathey Marsden added a comment - I opened DERBY-5308 for the client issue. Also I realized I should have been running with an insane build. Previous results were for a sane build.
        Hide
        Kathey Marsden added a comment -

        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:

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

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

        Show
        Kathey Marsden added a comment - 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 # largedata/LobLimits.java I'll open another issue to investigate if this test can be run for client now that these issues are fixed.
        Hide
        Kathey Marsden added a comment -

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

        Show
        Kathey Marsden added a comment - Assigning to myself to investigate. This issue was discussed on the list in this thread: http://old.nabble.com/Largedata-test-history-ts31963968.html
        Hide
        Kathey Marsden added a comment -

        moving description from environment to description

        Show
        Kathey Marsden added a comment - moving description from environment to description

          People

          • Assignee:
            Kathey Marsden
            Reporter:
            Myrna van Lunteren
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development