[ http://issues.apache.org/jira/browse/DERBY-810?page=comments#action_12363029 ]
Daniel John Debrunner commented on DERBY-810: --------------------------------------------- The SQLState constants are not part of the public api, tests should not be using them. In fact it's better if the test does have its own version of the constant as then a incorrect change in the code would be caugth be the test. Changing the SQL state for shutdown is a change in api. and could break existing applications. > intermittent diff for store/RecoveryAfterBackup.java test > --------------------------------------------------------- > > Key: DERBY-810 > URL: http://issues.apache.org/jira/browse/DERBY-810 > Project: Derby > Type: Test > Components: Store > Versions: 10.2.0.0 > Environment: Sun jdk 1.5 > Reporter: Kathey Marsden > Assignee: Øystein Grøvlen > Fix For: 10.2.0.0 > Attachments: derby-810.diff, derby-810.stat > > I saw this diff for test running at 2006-01-11 00:45:23 PST. The test seemed > to run fine the next night.It would appear that this is some sort of > intermittent test output problem. The test was just checked in on > 2006-01-09. > store/RecoveryAfterBackup.java. on jdk15 > *** Start: RecoveryAfterBackup jdk1.5.0_02 storeall:storerecovery 2006-01-11 > 00:45:23 *** > 4 del > < SQL Exception: Derby system shutdown. > 5 del > < Starting restore with roll-forward recovery.. > 5a4 > > SQL Exception: Derby system shutdown.Starting restore with roll-forward > > recovery.. > Test Failed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
