db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <j...@apache.org>
Subject [jira] Created: (DERBY-2586) BlobClob4BlobTest.tesPositionAgressive takes very long time
Date Tue, 24 Apr 2007 12:55:15 GMT
BlobClob4BlobTest.tesPositionAgressive takes very long time

                 Key: DERBY-2586
                 URL: https://issues.apache.org/jira/browse/DERBY-2586
             Project: Derby
          Issue Type: Bug
            Reporter: Øystein Grøvlen
         Assigned To: Øystein Grøvlen
             Fix For:

Dan reports that BlobClob4BlobTest.tesPositionAgressive takes very long to run:
> In a test run (junit-all) of 5,816 fixtures that took 4124 seconds (~68mins) *three*
fixtures took 53% of the total time.
> testPositionAgressive                1564.684 seconds
> testNetworkServerSecurityMechanism    497.280 seconds
> testTypesInActionStatement            128.928 seconds 

Knut Anders reports that this behavior is fairly new:
> It seems like it started taking a lot more time at revision 530085. I had
> run the tests at an earlier revision.

This was a check-in for DERBY-2346.  Since Anurag is currently on vacation, I will try to
look into this.

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

View raw message