You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2013/04/03 18:03:15 UTC
[jira] [Updated] (DERBY-6149) Long wait when 10.8
lang.SequenceGeneratorTest is run against 10.10 jars
[ https://issues.apache.org/jira/browse/DERBY-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-6149:
----------------------------------
Summary: Long wait when 10.8 lang.SequenceGeneratorTest is run against 10.10 jars (was: Hang when 10.8 lang.SequenceGeneratorTest is run against 10.10 jars)
> Long wait when 10.8 lang.SequenceGeneratorTest is run against 10.10 jars
> -------------------------------------------------------------------------
>
> Key: DERBY-6149
> URL: https://issues.apache.org/jira/browse/DERBY-6149
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.10.1.1
> Reporter: Kathey Marsden
>
> Using the 10.8 testing jar and the 10.10 product jars the 10.8 test lang.SequenceGeneratorTest has multiple failures and then hangs after test_07_dropSequence fails.
> To reproduce put the 10.8 derbyTesting.jar (latest on 10.8 branch) and 10.10.1.1 product jars in your classpath and run the junit test org.apache.derbyTesting.functionTests.tests.lang.SequenceGeneratorTest.
> ++ java -Xmx512M -Xms512M -Dderby.tests.debug=true -Dderby.tests.trace=true -Dderby.tests.basePort=1630 '-DderbyTesting.
> oldReleasePath=C:\cygwin\svnreleases\jars' junit.textui.TestRunner org.apache.derbyTesting.functionTests.tests.lang.Sequ
> enceGeneratorTest
> ++ tee rju.out
> DEBUG: {TC@55923149} basePort=1630, bogusPort=1631, jmxPort=1632
> DEBUG: {TC@55937944} basePort=1630, bogusPort=1631, jmxPort=1633
> .
> test_01_basic DEBUG: Preparing statement:
> create sequence seq_01
> DEBUG: Preparing statement:
> select currentvalue from sys.syssequences seq, sys.sysschemas s where s.schemaname = ? and seq.sequencename = ?
> and s.schemaid = seq.schemaid
> DEBUG: Preparing statement:
> values( next value for TEST_DBO.SEQ_01 )
> DEBUG: Preparing statement:
> select currentvalue from sys.syssequences seq, sys.sysschemas s where s.schemaname = ? and seq.sequencename = ?
> and s.schemaid = seq.schemaid
> used 723 ms F.
> test_02_boundary used 323 ms E.
> test_03_nonCycling used 315 ms E.
> test_04_reboot DEBUG: Preparing statement:
> create sequence seq_04
> DEBUG: Preparing statement:
> values( next value for TEST_DBO.SEQ_04 )
> DEBUG: Preparing statement:
> select currentvalue from sys.syssequences seq, sys.sysschemas s where s.schemaname = ? and seq.sequencename = ?
> and s.schemaid = seq.schemaid
> used 383 ms F.
> test_05_concurrency DEBUG: Preparing statement:
> create sequence seq_05
> DEBUG: Preparing statement:
> grant usage on sequence seq_05 to public
> DEBUG: Preparing statement:
> values( next value for TEST_DBO.SEQ_05 )
> DEBUG: Preparing statement:
> select currentvalue from sys.syssequences seq, sys.sysschemas s where s.schemaname = ? and seq.sequencename = ?
> and s.schemaid = seq.schemaid
> used 427 ms F.
> test_06_bigStepSize used 306 ms E.
> test_07_dropSequence DEBUG: Preparing statement:
> create sequence seq_07
> DEBUG: Preparing statement:
> values( next value for TEST_DBO.SEQ_07 )
> DEBUG: Preparing statement:
> select currentvalue from sys.syssequences seq, sys.sysschemas s where s.schemaname = ? and seq.sequencename = ?
> and s.schemaid = seq.schemaid
> used 330 ms F
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira