db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6533) Add a quiet mode to NsTest
Date Wed, 23 Apr 2014 13:26:15 GMT

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

Rick Hillegas updated DERBY-6533:

    Attachment: derby-6533-07-aa-moreDefensiveCode.diff

Attaching derby-6533-aa-anotherNPE.diff. This patch adds some more defensive code to NsTest.
This patch also adds timestamps to exception summaries. Now for each exception, we report
the time of its first occurrence and the time of its last occurrence.

Touches the following files:

M       java/testing/org/apache/derbyTesting/system/nstest/NsTest.java
M       java/testing/org/apache/derbyTesting/system/nstest/tester/TesterObject.java
M       java/testing/org/apache/derbyTesting/system/nstest/NsTestError.java

> 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:
>            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-aa-anotherNPE.diff,
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

View raw message