[jira] Issue Comment Edited: (DERBY-1764) Rewrite stress.multi as a JUnit test

["Erlend Birkenes (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614608#action_12614608 ] 

ebirkenes edited comment on DERBY-1764 at 7/17/08 7:58 PM:
-----------------------------------------------------------------

Edit: Hmm, Jira doesn't handle quoting so well.. Or is it Gmails fault?

On 7/6/08, Kathey Marsden (JIRA) <ji...@apache.org> wrote:


>    1) There seems to be an issue with the cleanup of the database for the encrypted run on windows.  I saw this with both the 10x1 and the regular StressMultiTest.
>      (junit.framework.AssertionFailedError: C:\svn3\trunk\system\singleUse\oneuse0\seg0\c400.dat)


I don't have a Windows box, but maybe I can set something up. Is anyone else getting this error?


 >   3) Bryan is seeing the test run forever for some reason and also seeing lots of output. It sounds like maybe he was using an early patch,  but need to resolve this.


Still have no clue about this. Is nobody else seeing this behaviour?
 


>    4) The test seems to expose a derby bug intermittently. .DERBY-3757.
>    )testStressMulti(org.apache.derbyTesting.functionTests.tests.multi.StressMultiTest)java.sql.SQLException: Java exception: 'ASSERT FAILED transaction table has null entry:  org.apache.derby.shared.common.sanity.AssertFailure'.


This happened once for me, but I couldn't reproduce it.
 


>   5) StressMulti50x59 should only do an embedded run.


 Fixed in DERBY-1764_V4.diff

>    6) I noticed when I got the error for DERBY-3757 that the derby.log was not saved to the fail  directory.  There seems to be a problem with the mechanism that is supposed to do this.  Is it possible it only saves the derby.log for failures and not errors?


 Fixed in DERBY-1764_V4.diff


      was (Author: ebirkenes):
    

I don't have a Windows box, but maybe I can set something up. Is anyone else
getting this error?




Still have no clue about this. Is nobody else seeing this behaviour?




This happened once for me, but I couldn't reproduce it.




 Fixed in DERBY-1764_V4.diff

6) I noticed when I got the error for DERBY-3757 that the derby.log was not


 Fixed in DERBY-1764_V4.diff

  
> Rewrite stress.multi as a JUnit test
> ------------------------------------
>
>                 Key: DERBY-1764
>                 URL: https://issues.apache.org/jira/browse/DERBY-1764
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>            Reporter: Knut Anders Hatlen
>            Assignee: Erlend Birkenes
>         Attachments: derby-1764-3a-whitespace_changes.diff, derby-1764-derby.log, DERBY-1764-Review.diff, DERBY-1764-V1.diff, DERBY-1764-V2.diff, DERBY-1764_4.diff
>
>
> Currently, stress.multi consists of a number of sql scripts that are run in ij. It often fails with cryptic error messages, and since it uses ij, there is often no stack trace. It would be very useful to rewrite the test in JUnit so that we can get better error messages and stack traces when it fails.

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