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] Commented: (DERBY-496) unit test 'org.apache.derbyTesting.unitTests.services.T_Diagnosticable' was failed
Date Sat, 06 Aug 2005 07:07:35 GMT
    [ http://issues.apache.org/jira/browse/DERBY-496?page=comments#action_12317836 ] 

Tomohito Nakayama commented on DERBY-496:
-----------------------------------------

I suspected exception which was not assumed was happened in the "org.apache.derby.iapi.services.diag.DiagnosticUtil#findDiagnostic(Object
ref)" , 
which was called from  "toDiagString(Object obj)" of the same class.


On this assumption, I added next test code to working copy:

Index: DiagnosticUtil.java
===================================================================
--- DiagnosticUtil.java	(revision 230523)
+++ DiagnosticUtil.java	(working copy)
@@ -78,6 +78,8 @@
 				String          diagClassName = 
 					className.substring(0, lastDot) + 
 					"D_" + className.substring(lastDot);
+				
+				System.out.println("SURVEY-496: " + diagClassName);
 
 				Class diagClass;
 				
@@ -98,10 +100,14 @@
 
 				diag_obj.init(ref);
 
+				System.out.println("SURVEY-496: diag_obj found");
+
 				return diag_obj;
 			}
 			catch (Exception e)
 			{
+				System.out.println("SURVEY-496:exepction catched");
+				e.printStackTrace(System.out);
 				return null;
 			}
 		}


Next is log of executing program with test code:

text:MasterFileName = master/T_Diagnosticable.out
2 del
< -- Unit Test T_Diagnosticable finished
2 add
> SURVEY-496: org.apache.derbyTesting.unitTests.services.D_T_DiagTestClass1
> SURVEY-496:exepction catched
> java.lang.SecurityException: sealing violation: package org.apache.derby.iapi.services.diag
is sealed
> Shutting down due to unit test failure.
Test Failed.
*** End:   T_Diagnosticable jdk1.4.2_08 2005-08-06 15:41:06 ***


 I guesses java.lang,SecurityException. which was found in the log . causes this phenomena.

> 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
>     Assignee: Tomohito Nakayama
>  Attachments: derby.log
>
> 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