[DERBY-3873] Intermittent failures in 'ttestSetPortPriority(o.a.dT.fT.tests.derbynet.ServerPropertiesTest)'

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Cannot Reproduce
• Affects Version/s: 10.4.2.1, 10.5.1.1
• Component/s: Test
• Labels: derby_triage10_8
• Environment: trunk - 1.6 - sles, lin, sol; trunk - 1.5 - lin; 10.4 - 1.6 - lin
• Urgency: Normal
• Bug behavior facts: Regression Test Failure
• Assignee: Unassigned
• Reporter: Ole Solberg
• Created: 11/Sep/08 07:41
• Updated: 23/Jan/15 00:31
• Resolved: 23/Jan/15 00:31

Description

a) ttestSetPortPriority(org.apache.derbyTesting.functionTests.tests.derbynet.ServerPropertiesTest)junit.framework.AssertionFailedError: Can not ping server specified with -p
and
b) ttestSetPortPriority(org.apache.derbyTesting.functionTests.tests.derbynet.ServerPropertiesTest)junit.framework.AssertionFailedError: Can still ping server specified with -p

First seen 608645 2008-01-03 http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/608645-org.apache.derbyTesting.functionTests.suites.All_diff.txt
Then mistakenly linked to DERBY-3088.

See http://dbtg.thresher.com/derby/test/stats_newest.html for occurences.

Issue Links

• is related to: DERBY-5610 ServerPropertiesTest prints .java.net.SocketException: Connection reset to console but test passes
• is related to: DERBY-4347 Provide a property to increase network server start timeout for JUnit tests