[
https://issues.apache.org/jira/browse/DERBY-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-2076:
-----------------------------------
Attachment: derby-2076-0b-modernized_compat_test_preview.diff
Attaching an updated version of the modernized compatibility test. Here's what
running the MATS looks like (with trace and debug enabled):
$ java -cp
"..\jars\sane\derbyrun.jar;..\jars\sane\derbyTesting.jar;..\tools\java\junit.jar"
-DderbyTesting.oldReleasePath=$( cygpath --windows
~/winhome/Documents/derby/releases ) -Dderby.tests.trace=true
junit.textui.TestRunner
org.apache.derbyTesting.functionTests.tests.compatibility._Suite
{ReleaseRepository} 19 candidate releases at
C:\Users\kwaagan\Documents\derby\releases
skipped invalid distribution: C:\Users\kwaagan\Documents\derby\releases\10.0.2.1
.
(net)compatibility.ClientCompatibilityRunControl.client 10.10.0.0 <> server
10.10.0.0 used 4134 ms .
(net)compatibility.ClientCompatibilityRunControl.client 10.8.2.2 <> server
10.10.0.0 used 2091 ms .
(net)compatibility.ClientCompatibilityRunControl.client 10.7.1.1 <> server
10.10.0.0 used 2074 ms .
(net)compatibility.ClientCompatibilityRunControl.client 10.6.2.1 <> server
10.10.0.0 used 2075 ms .
(net)compatibility.ClientCompatibilityRunControl.client 10.5.3.0 <> server
10.10.0.0 used 1576 ms .
(net)compatibility.ClientCompatibilityRunControl.client 10.4.2.0 <> server
10.10.0.0 used 1575 ms .
(net)compatibility.ClientCompatibilityRunControl.client 10.3.3.0 <> server
10.10.0.0 used 1576 ms .
(net)compatibility.ClientCompatibilityRunControl.client 10.2.2.0 <> server
10.10.0.0 used 1560 ms .
(net)compatibility.ClientCompatibilityRunControl.client 10.1.3.1 <> server
10.10.0.0 used 1560 ms .
(net)compatibility.ClientCompatibilityRunControl.client 10.10.0.0 <> server
10.8.2.2 used 3634 ms .
(net)compatibility.ClientCompatibilityRunControl.client 10.10.0.0 <> server
10.7.1.1 used 3120 ms .
(net)compatibility.ClientCompatibilityRunControl.client 10.10.0.0 <> server
10.6.2.1 used 3120 ms .
(net)compatibility.ClientCompatibilityRunControl.client 10.10.0.0 <> server
10.5.3.0 used 3104 ms .
(net)compatibility.ClientCompatibilityRunControl.client 10.10.0.0 <> server
10.4.2.0 used 3136 ms .
(net)compatibility.ClientCompatibilityRunControl.client 10.10.0.0 <> server
10.3.3.0 used 3634 ms .
(net)compatibility.ClientCompatibilityRunControl.client 10.10.0.0 <> server
10.2.2.0 used 2605 ms .
(net)compatibility.ClientCompatibilityRunControl.client 10.10.0.0 <> server
10.1.3.1 used 3120 ms
Time: 73,692
OK (17 tests)
This is still not ready for commit.
Given this will be enabled by default in suites.All, do people prefer that the
test fails if there are no old releases available, or rather that an ALARM
statement is printed?
> 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,
> derby-2076-0b-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
