Mike Matrigali wrote: > I submitted a fix for this yesterday, let me know if it still is an > issue after getting update. >
It's OK after my update this evening.
Mike Matrigali wrote:
What kind of machine/OS are you running on. I ran all the tests and they passed. And I have been checking results of a number of test runs on different machines and OS's and never saw that error. I would have expected the debug messages to only go into derby.log and not show up in test output.
It seems somehow in your environment stuff meant to go into derby.log is somehow going to standard output instead?
You're probably right in that it's due to a problem with my environment...
In the sources I saw some references to derby.log vs standard output but I didn't look into the details. I will investigate this. Do you have any hints?
-- Ole
