[ 
https://issues.apache.org/jira/browse/DERBY-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mamta A. Satoor updated DERBY-4361:
-----------------------------------

    Fix Version/s: 10.4.2.1

backported the changes to 10.4 codeline

> testDefault fixture in engine.ErrorStreamTest has been failing with 
> junit.framework.AssertionFailedError: File 
> C:\jartest\JarResults.XXdateXX\ibm15_suites.All\system\derby.log could not be 
> deleted
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4361
>                 URL: https://issues.apache.org/jira/browse/DERBY-4361
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.5.3.1, 10.6.0.0
>            Reporter: Mamta A. Satoor
>             Fix For: 10.4.2.1, 10.5.3.1
>
>         Attachments: mamta.java
>
>
> testDefault fixture has been failing atleast since August 18th 2009 with 
> following exception. I do not have access to test results fro 15th, 16th and 
> 17th so not sure if the failure started earlier. It seemed to have run find 
> on August 14th 2009.
> 1) 
> testDefault(org.apache.derbyTesting.functionTests.tests.engine.ErrorStreamTest)junit.framework.AssertionFailedError:
>  File C:\jartest\JarResults.2009-08-18\ibm15_suites.All\system\derby.log 
> could not be deleted
>       at 
> org.apache.derbyTesting.functionTests.tests.engine.ErrorStreamTest.testDefault(ErrorStreamTest.java:135)
>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>       at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
>       at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>       at 
> org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:109)
> This is happening both on trunk and 10.5 codelines. Not sure of other 
> codelines. The failure appears on Windows but not on Linux. The jvms that 
> definitely show the failures are ibm 15 and ibm16
> Does anyone know of the cause of the failure?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to