[
https://issues.apache.org/jira/browse/DERBY-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610826#action_12610826
]
Kathey Marsden commented on DERBY-1764:
---------------------------------------
I checked in the test so others can try it. Thanks Erlend for all your hard
work on this.
Here are the issues I see.
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)
2) Need to add functionality so that if threads hang and cannot finish on their
own, we dump the stack traces and interrupt the threads. I think this is
important as when we have had failures in this test in the past, we have seen
the threads hang.
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.
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'.
5) StressMulti50x59 should only do an embedded run.
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?
I hope others will try out the test as well now that it is checked in and
review the code. This is an important test and is a fairly major change.
It's important we get it right.
Kathey
> 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-derby.log, DERBY-1764-Review.diff,
> DERBY-1764-V1.diff, DERBY-1764-V2.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.
