Details

    • Type: Sub-task Sub-task
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 10.1.2.1
    • Fix Version/s: None
    • Component/s: Test
    • Urgency:
      Normal
    • Issue & fix info:
      Newcomer

      Description

      the largeCodeGen test needs to be expanded to include other cases that genreate large amounts of byte code.

      For example:
      large in clause
      large insert statement that inserts many rows
      sql statements with large constant values

      It is best if the verious tests just use a variable that can be bumped higher and higher for testing and if individual cases are isolated.

      Possible approaches, think of ways to make sql statements really big that will take different code paths.

      Look in the code for instances of statementNumHitLimit and create cases that pass through that code. Those cases may pass but the hope is to get rid of these calls in favor of splitting the code in a centralized way, so add the tests to largeCodeGen even if they don't fail.

        Activity

        Hide
        Kathey Marsden added a comment -

        I pulled the largeCodeGen test into the largeData suite. I suppressed the exception output for failed cases by default. It varies from run to run and jvm to jvm. There is a boolean PRINT_FAILURE_EXCEPTION that can be turned on for debugging.

        I am curious. Is there anyone out there that runs the largeData test from time to time? What are the system requirements?

        Show
        Kathey Marsden added a comment - I pulled the largeCodeGen test into the largeData suite. I suppressed the exception output for failed cases by default. It varies from run to run and jvm to jvm. There is a boolean PRINT_FAILURE_EXCEPTION that can be turned on for debugging. I am curious. Is there anyone out there that runs the largeData test from time to time? What are the system requirements?
        Hide
        Sunitha Kambhampati added a comment -

        I remember the last time I ran the largeData with ibm142 a couple months ago, this suite passed OK. Now, I ran the largeData suite with the ibm 1.5 jvm and the largeCodeGen test in embedded mode fails on linux 2.6 kernel, rhel4.

        There is some discussion on the list about this test failing with client but passes with embedded. I see in the earlier comment - Kathey mentioned that the failed cases (i think ) varies for different jvm to jvm, run to run.

        – Has this test ever run successfully before ?
        – Is it expected that the test output will vary ? if so, then how do we ensure no regression has happened - is there some way to know that. ? Should this test be enabled as part of largeData ?

        Thanks.

        Show
        Sunitha Kambhampati added a comment - I remember the last time I ran the largeData with ibm142 a couple months ago, this suite passed OK. Now, I ran the largeData suite with the ibm 1.5 jvm and the largeCodeGen test in embedded mode fails on linux 2.6 kernel, rhel4. There is some discussion on the list about this test failing with client but passes with embedded. I see in the earlier comment - Kathey mentioned that the failed cases (i think ) varies for different jvm to jvm, run to run. – Has this test ever run successfully before ? – Is it expected that the test output will vary ? if so, then how do we ensure no regression has happened - is there some way to know that. ? Should this test be enabled as part of largeData ? Thanks.
        Hide
        Kathey Marsden added a comment -

        With revision 37644 I fixed the run to run differences and at that time the test passed with both embedded and client on Windows. I never tried on Linux.

        With revision 377609 Dan was able to move the number of parameters in the in list query from 3400 to 97000 (amazing). I don't know if it passed with client at that time.

        Raman's testing shows that client fails before 97000 with client.
        Raman what is the highest number it goes to with client and what is the error and stack trace when it fails? In the test there is a boolean PRINT_FAILURE_EXCEPTION that you will have to change to see the failure.

        Show
        Kathey Marsden added a comment - With revision 37644 I fixed the run to run differences and at that time the test passed with both embedded and client on Windows. I never tried on Linux. With revision 377609 Dan was able to move the number of parameters in the in list query from 3400 to 97000 (amazing). I don't know if it passed with client at that time. Raman's testing shows that client fails before 97000 with client. Raman what is the highest number it goes to with client and what is the error and stack trace when it fails? In the test there is a boolean PRINT_FAILURE_EXCEPTION that you will have to change to see the failure.
        Hide
        Daniel John Debrunner added a comment -

        The insert case is included in largeCodeGen now.

        Show
        Daniel John Debrunner added a comment - The insert case is included in largeCodeGen now.
        Hide
        Myrna van Lunteren added a comment -

        Marking newcomer, I think this should be doable.
        Unfortunately, I've had trouble running the largeDataTests recently, but assuming they can be made to work, more functionality could be added there.
        Also, perhaps this issue can be split into further issues as some of the functionality/testing desired has been implemented...

        Show
        Myrna van Lunteren added a comment - Marking newcomer, I think this should be doable. Unfortunately, I've had trouble running the largeDataTests recently, but assuming they can be made to work, more functionality could be added there. Also, perhaps this issue can be split into further issues as some of the functionality/testing desired has been implemented...

          People

          • Assignee:
            Unassigned
            Reporter:
            Kathey Marsden
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development