TomohitoNakayama wrote: > Hello. > >>> I think we may ignore error message in this case. >> >> >> Perhaps then the easiest solution for this test is to specify a >> PrintWriter for console output in this line of the test instead of null. >> That way the error output could go to a file. >> This would be the affected line of code. >> >> networkServer.start(null); > > > I see .... > It may be needed to check the file of error output whether any other > Exception was found in that file .... >
Just FYI For most tests, the test harness starts the network server and the console output goes to DerbyNet.out. As far as I know none of the tests check either the DerbyNet.out output or the derby.log, but rather just whatever behavior they are testing. This test starts it's own embedded network server instead of letting the test harness start it so has to specify it's own console output location.
