db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomohito Nakayama (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-496) unit test 'org.apache.derbyTesting.unitTests.services.T_Diagnosticable' was failed
Date Sat, 06 Aug 2005 04:24:35 GMT
unit test 'org.apache.derbyTesting.unitTests.services.T_Diagnosticable' was failed
----------------------------------------------------------------------------------

         Key: DERBY-496
         URL: http://issues.apache.org/jira/browse/DERBY-496
     Project: Derby
        Type: Bug
 Environment: naka@nysalor:~$ cat /proc/version
Linux version 2.4.27-2-386 (horms@tabatha.lab.ultramonkey.org) (gcc version 3.3. 5 (Debian
1:3.3.5-12)) #1 Mon May 16 16:47:51 JST 2005

naka@nysalor:~$ java -version
java version "1.4.2_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03)
Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)

    Reporter: Tomohito Nakayama


As summary.


I found next exception in derby.log.

[main] FAIL - org.apache.derbyTesting.unitTests.harness.T_Fail: Test failed - DiagnosticUtil.toDiagString()
failed, got: (T_DiagTestClass1.toString(): object with diag interface), expected: (D_T_DiagTestClass1:
object with diag interface).
org.apache.derbyTesting.unitTests.harness.T_Fail: Test failed - DiagnosticUtil.toDiagString()
failed, got: (T_DiagTestClass1.toString(): object with diag interface), expected: (D_T_DiagTestClass1:
object with diag interface).
	at org.apache.derbyTesting.unitTests.harness.T_Fail.testFailMsg(T_Fail.java:95)
	at org.apache.derbyTesting.unitTests.services.T_Diagnosticable.t_001(T_Diagnosticable.java:105)
	at org.apache.derbyTesting.unitTests.services.T_Diagnosticable.runTestSet(T_Diagnosticable.java:207)
	at org.apache.derbyTesting.unitTests.harness.T_MultiIterations.runTests(T_MultiIterations.java:94)
	at org.apache.derbyTesting.unitTests.harness.T_Generic.Execute(T_Generic.java:117)
	at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.runATest(BasicUnitTestManager.java:183)
	at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.runTests(BasicUnitTestManager.java:245)
	at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.boot(BasicUnitTestManager.java:92)
	at org.apache.derby.impl.services.monitor.BaseMonitor.boot(BaseMonitor.java:1996)
	at org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java:290)
	at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1834)
	at org.apache.derby.impl.services.monitor.BaseMonitor.startServices(BaseMonitor.java:966)
	at org.apache.derby.impl.services.monitor.BaseMonitor.runWithState(BaseMonitor.java:398)
	at org.apache.derby.impl.services.monitor.FileMonitor.<init>(FileMonitor.java:57)
	at org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Monitor.java:288)
	at org.apache.derbyTesting.unitTests.harness.UnitTestMain.main(UnitTestMain.java:50)


-- 
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


Mime
View raw message