[
https://issues.apache.org/jira/browse/DERBY-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213222#comment-13213222
]
Myrna van Lunteren commented on DERBY-2076:
-------------------------------------------
The test failure that - briefly - sparked my interest was on January 26, with
ibm 1.7, on windows:
http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm17/1236495-derbyall_diff.txt
The diff is:
-----------------
*** Start: CompatibilityTest jdk1.7.0 DerbyNetClient
derbynetclientmats:derbynetclientmats 2012-01-27 03:32:29 ***
0 add
> Exception in thread "main" java.sql.SQLException: java.net.ConnectException :
> Error connecting to server xxxFILTERED_HOSTNAMExxx on port 1527 with message
> Connection refused: connect.
> Caused by: org.apache.derby.client.am.DisconnectException:
> java.net.ConnectException : Error connecting to server
> xxxFILTERED_HOSTNAMExxx on port 1527 with message Connection refused: connect.
> ... 8 more
> Caused by: java.net.ConnectException: Connection refused: connect
> ... 14 more
Test Failed.
----------------------------
Unfortunately, I don't have any further details - the test directory has been
lost by now.
This test does not fail frequently. In fact, I checked and don't see records of
it failing at all last year, and only the once this year. So this doesn't have
high priority for me.
I have no patch to contribute.
> Rewrite junitTests/derbyNet/CompatibilityTest to conform to current JUnit
> usage
> -------------------------------------------------------------------------------
>
> Key: DERBY-2076
> URL: https://issues.apache.org/jira/browse/DERBY-2076
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.3.1.4
> Reporter: Andrew McIntyre
> Assignee: Kristian Waagan
> Priority: Minor
> Attachments: derby-2076-0a-modernized_compat_test_preview.diff
>
>
> The test
> org.apache.derbyTesting.functionTests.tests.junitTests.DerbyNet.CompatibilityTest
> has been failing in the nightlies because it needs to be run in the old test
> harness, and for some reason the property which grants permission to read
> ${user.home}/junit.properties is not being picked up properly in the old
> harness.
> I am able to resolve the problem by granting permission to read
> ${user.home}/junit.properties to all, but the test should be refactored so
> that it can run with the rest of the junit tests without needing the old
> harness.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
