[jira] [Updated] (DERBY-6533) Add a quiet mode to NsTest

["Rick Hillegas (JIRA)" <ji...@apache.org>]

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

Rick Hillegas updated DERBY-6533:
---------------------------------

    Attachment: nstest.out

Attaching the log from today's 6 hour run of NsTest on the 8 core machine using the latest patch.

Summary: No timeouts. But there were 6 deadlocks 24 minutes into the test. The deadlocks involved the user table and SYSDEPENDS and occurred while running a delete trigger.

> Add a quiet mode to NsTest
> --------------------------
>
>                 Key: DERBY-6533
>                 URL: https://issues.apache.org/jira/browse/DERBY-6533
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.11.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-6533-01-aa-quietMode.diff, derby-6533-02-aa-sequencesAndMoreStats.diff, derby-6533-02-aa-sequencesAndMoreStats.out, derby-6533-03-timerThread.diff, derby-6533-04-outOfMemory.diff, derby-6533-05-aa-dieQuickly.diff, derby-6533-07-aa-moreDefensiveCode.diff, derby-6533-08-aa-sortErrors.diff, derby-6533-aa-anotherNPE.diff, nstest.out, nstest.out, nstest.out, nstest.out, nstest.out, nstest.out, nstest.out, nstest.out, nstest.out, nstest.out, nstest.out, nstest.out
>
>
> Right now NsTest produces an enormous log file. This may be useful for tracking down some errors. However, this can also make it hard to find the signal in the noise. It would be good to turn off the chatty diagnostics which report the result of every insert, update, delete, and select. A summary at the end may be good enough, including a summary of the number of times each kind of error (SQLState) was seen. While I'm in there, I plan to make other smallish changes.



--
This message was sent by Atlassian JIRA
(v6.2#6252)