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

Ramin Moazeni commented on DERBY-1272:
--------------------------------------

I was getting the following error which indicates that the 
derby.stream.error.logSeverityLevel property 
has not been set to 0. When I ran the test individually or _Suite, the test(s) 
completed successfully.
Therefore, I changed the test order and got a successful run.

There were 2 failures:
1) 
testDerbyLog(org.apache.derbyTesting.functionTests.tests.tools.DerbyLogTest)junit.framework.ComparisonFailure:
 expected:<------------------ Java Information ------------------> but 
was:<java.sql.SQLException: Database 'wombat' not found.>
        at 
org.apache.derbyTesting.functionTests.tests.tools.DerbyLogTest.testDerbyLog(DerbyLogTest.java:110)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at 
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:95)
2) 
testDerbyLog(org.apache.derbyTesting.functionTests.tests.tools.DerbyLogTest)junit.framework.ComparisonFailure:
 expected:<------------------ Java Information ------------------> but 
was:<java.sql.SQLException: Database 'wombat' not found.>
        at 
org.apache.derbyTesting.functionTests.tests.tools.DerbyLogTest.testDerbyLog(DerbyLogTest.java:110)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at 
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:95)
        at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
        at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
        at junit.extensions.TestSetup.run(TestSetup.java:23)
        at 
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
        at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
        at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
        at junit.extensions.TestSetup.run(TestSetup.java:23)

FAILURES!!!
Tests run: 74,  Failures: 2,  Errors: 0



> Change sysinfo to print to error log (derby.log) on boot of derby  if 
> derby.stream.error.logSeverityLevel=0
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1272
>                 URL: https://issues.apache.org/jira/browse/DERBY-1272
>             Project: Derby
>          Issue Type: Improvement
>          Components: Tools
>    Affects Versions: 10.1.2.1, 10.1.3.1, 10.2.1.6
>            Reporter: Kathey Marsden
>            Assignee: Ramin Moazeni
>            Priority: Minor
>         Attachments: derby-1272-pre.diff, derby-1272-pre2.diff, 
> derby-1272-pre3.diff, derby-1272-v4.diff, DERBY-1272v5.diff, 
> DERBY-1272v6.diff, DERBY-1272v6.stat
>
>
> It is often very difficult to collect correct sysinfo output from user 
> environments because  sysinfo run from the commandline does not have the same 
> classpath as the jvm that started Derby or Derby was loaded with a custom 
> classloader.
> It would be very helpful in assisting users in diagnosing their issues if 
> sysinfo dumped to the error log if  derby.stream.error.logSeverityLevel=0  or 
> even by default.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to