db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Thalamati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1346) unit/fillLog.unit seems to be failed if program was build as sane.
Date Fri, 26 May 2006 21:33:31 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1346?page=comments#action_12413535 ] 

Suresh Thalamati commented on DERBY-1346:
-----------------------------------------

After bit of search , found this test is failing after the following change to the code line.


r407642 | fuzzylogic | 2006-05-18 14:56:36 -0700 (Thu, 18 May 2006) | 4 lines

DERBY-892: Allow for test-specific additions to the derby_tests.policy file.

Committed for Myrna Van Lunteren <m.v.lunteren@gmail.com>

------------------------------------------------------------------------


Thanks
-suresh


> unit/fillLog.unit seems to be failed if program was build as sane.
> ------------------------------------------------------------------
>
>          Key: DERBY-1346
>          URL: http://issues.apache.org/jira/browse/DERBY-1346
>      Project: Derby
>         Type: Bug

>  Environment: naka@rufelza:~/derby/test/20060525_2$ cat /proc/version 
> Linux version 2.6.12-1-386 (horms@tabatha.lab.ultramonkey.org) (gcc version 4.0.2 20050917
(prerelease) (Debian 4.0.1-8)) #1 Tue Sep 27 12:41:08 JST 2005
> naka@rufelza:~/derby/test/20060525_2$ java -version
> java version "1.4.2_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_10-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_10-b03, mixed mode)
>     Reporter: Tomohito Nakayama

>
> I found unit/fillLog.unit is failed when program was build as sane.
> I found exception was recorded in derby.log as next.
> naka@rufelza:~/derby/test/20060525/fillLog$ cat derby.log 
> 2006-05-25 13:31:31.682 GMT Thread[main,5,main] Starting test  'org.apache.derbyTesting.unitTests.store.T_RecoverFullLog'.
> [main]     _______________________________________________________
> [main]     
> 		cleaning up database for recovering from filled log
> [main]     _______________________________________________________
> ----------------------------------------------------------------
> 2006-05-25 13:31:31.758 GMT:
>  Booting Derby version The Apache Software Foundation - Apache Derby - 10.2.0.0 alpha
- (409175M): instance c013800d-010b-6bbe-25d9-ffff8dd9044f
> on database directory /home/naka/derby/test/20060525/fillLog/FullLogTest  
> [main]     	container 0:1148563891732 pages: 2 3 4 5 6 7 8 
> [main]     	container 1:1148563891733 pages: 2 3 4 5 6 7 8 
> [main]     	container 2:1148563891734 pages: 2 3 4 5 6 7 8 
> [main]     	container 3:1148563891735 pages: 2 3 4 5 6 7 8 
> [main]     	container 4:1148563891736 pages: 2 3 4 5 6 7 8 
> [main]     	container 5:1148563891737 pages: 2 3 4 5 6 7 8 
> [main]     	container 6:1148563891738 pages: 2 3 4 5 6 7 8 
> [main] FAIL - org.apache.derbyTesting.unitTests.harness.T_Fail: Test failed - log should
have filled but did not
> org.apache.derbyTesting.unitTests.harness.T_Fail: Test failed - log should have filled
but did not
> 	at org.apache.derbyTesting.unitTests.harness.T_Fail.testFailMsg(T_Fail.java:95)
> 	at org.apache.derbyTesting.unitTests.store.T_RecoverFullLog.fillUpLog(T_RecoverFullLog.java:711)
> 	at org.apache.derbyTesting.unitTests.store.T_RecoverFullLog.runTests(T_RecoverFullLog.java:298)
> 	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:1831)
> 	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:59)
> 	at org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Monitor.java:288)
> 	at org.apache.derbyTesting.unitTests.harness.UnitTestMain.main(UnitTestMain.java:50)
> 2006-05-25 13:31:32.605 GMT Thread[main,5,main] Test 'org.apache.derbyTesting.unitTests.store.T_RecoverFullLog'
failed
> 2006-05-25 13:31:32.605 GMT Thread[main,5,main] Test Summary - Run 1, Passed 0, Failed
1, Skipped 0.
> 2006-05-25 13:31:32.605 GMT Thread[main,5,main] Shutting down due to unit test failure,
see log for more information.
> 2006-05-25 13:31:32.965 GMT:
> Shutting down instance c013800d-010b-6bbe-25d9-ffff8dd9044f
> ----------------------------------------------------------------
> 2006-05-25 13:31:32.973 GMT Thread[main,5,main] Cleanup action starting
> ERROR XBM01: Startup failed due to an exception. See next exception for details. 
> 	at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:297)
> 	at org.apache.derby.iapi.services.monitor.Monitor.exceptionStartingModule(Monitor.java:668)
> 	at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1849)
> 	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:59)
> 	at org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Monitor.java:288)
> 	at org.apache.derbyTesting.unitTests.harness.UnitTestMain.main(UnitTestMain.java:50)
> ============= begin nested exception, level (1) ===========
> java.lang.NullPointerException
> 	at org.apache.derby.impl.services.monitor.TopService.getService(TopService.java:129)
> 	at org.apache.derby.impl.services.monitor.BaseMonitor.shutdown(BaseMonitor.java:197)
> 	at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.boot(BasicUnitTestManager.java:102)
> 	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:1831)
> 	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:59)
> 	at org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Monitor.java:288)
> 	at org.apache.derbyTesting.unitTests.harness.UnitTestMain.main(UnitTestMain.java:50)
> ============= end nested exception, level (1) ===========
> Cleanup action completed
> 2006-05-25 13:31:32.976 GMT Thread[main,5,main] 2006-05-25 13:31:32.976 GMT Thread[main,5,main]
Startup failed due to an exception. See next exception for details. 
> ERROR XBM01: Startup failed due to an exception. See next exception for details. 
> 	at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:297)
> 	at org.apache.derby.iapi.services.monitor.Monitor.exceptionStartingModule(Monitor.java:668)
> 	at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1849)
> 	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:59)
> 	at org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Monitor.java:288)
> 	at org.apache.derbyTesting.unitTests.harness.UnitTestMain.main(UnitTestMain.java:50)
> ============= begin nested exception, level (1) ===========
> java.lang.NullPointerException
> 	at org.apache.derby.impl.services.monitor.TopService.getService(TopService.java:129)
> 	at org.apache.derby.impl.services.monitor.BaseMonitor.shutdown(BaseMonitor.java:197)
> 	at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.boot(BasicUnitTestManager.java:102)
> 	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:1831)
> 	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:59)
> 	at org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Monitor.java:288)
> 	at org.apache.derbyTesting.unitTests.harness.UnitTestMain.main(UnitTestMain.java:50)
> ============= end nested exception, level (1) ===========

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