[
https://issues.apache.org/jira/browse/DERBY-5301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092334#comment-13092334
]
Bryan Pendleton commented on DERBY-5301:
----------------------------------------
The test failures that you are seeing in your run are due to two reasons:
1) First, the output of SYSCS_GET_RUNTIMESTATISTICS contains literal tab
characters (^I), but
your test program in the patch contains spaces. When I changed
TableLockBasicTest.java to contain
the expected tab characters in the right places, the test passes in one
configuration (embedded?) but
fails in the other configuration (client/server?) -- I may have the two
configurations backward.
2) The remaining test failure is because the statement name is null in one
configuration but is
SQL_CURLH000C3 in the other configuration. That is, the remaining test failure
that I see is:
1,2c1,2
< Expected: >Statement Name:
< null
---
> Found: >Statement Name:
> SQL_CURLH000C3
Perhaps you could get around that by using
if (getTestConfiguration().getJDBCClient().isEmbedded())
to build a different expected result string for each configuration?
I'll attach the version of TableLockBasicTest.java that I've been fiddling with
for you to
see what I did to make the tests pass.
thanks,
bryan
> Convert store/TableLockBasic.sql to junit
> ------------------------------------------
>
> Key: DERBY-5301
> URL: https://issues.apache.org/jira/browse/DERBY-5301
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Houx Zhang
> Assignee: Houx Zhang
> Labels: gsoc2011
> Attachments: 5301-1-part.patch, junit.out
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
