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

Knut Anders Hatlen commented on DERBY-5311:
-------------------------------------------

I added ij4Test to i18n._Suite before the other tests in the suite, and then I 
could reproduce the failures by running only that suite. resetWidth.txt fixed 
the failures, so +1 to that patch. (The maximumdisplaywidth command affecting 
all ij sessions in the JVM might perhaps be considered a bug, but fixing that 
is outside the scope of this JIRA.)

The noSecMgr.txt patch also looks like an improvement. Since there's no special 
setup in ij4Test after those changes, I don't think there's anything stopping 
us from adding it to ToolScripts and removing the ij4Test class. Hopefully the 
same could be done with the other ij*.sql tests.

> Convert tools/ij4.sql  to junit
> -------------------------------
>
>                 Key: DERBY-5311
>                 URL: https://issues.apache.org/jira/browse/DERBY-5311
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>            Reporter: Houx Zhang
>            Assignee: Houx Zhang
>              Labels: gsoc2011
>         Attachments: 5311-1.patch, 5311-1.stat, 5311-followup.txt, 
> noSecMgr.txt, resetWidth.txt, sysprop.diff
>
>


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to