You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/03/13 22:48:24 UTC
[jira] Created: (DERBY-3534) Run 10.3 tests against 10.4 to help
identify any compatibility issues
Run 10.3 tests against 10.4 to help identify any compatibility issues
---------------------------------------------------------------------
Key: DERBY-3534
URL: https://issues.apache.org/jira/browse/DERBY-3534
Project: Derby
Issue Type: Task
Components: Test
Affects Versions: 10.4.0.0
Reporter: Kathey Marsden
Assignee: Kathey Marsden
Priority: Minor
It would be good to run the 10.3 tests against 10.4 to identify any compat issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3534) Run 10.3 tests against 10.4 to help
identify any compatibility issues
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578547#action_12578547 ]
Kathey Marsden commented on DERBY-3534:
---------------------------------------
I'd have to go back and look more closely. I ported most of change 632502 to my 10.3
client and hacked the server enough to get derbyTesting.jar to build and ran tests.
I will attach the results. I have yet to look at them in detail:
> Run 10.3 tests against 10.4 to help identify any compatibility issues
> ---------------------------------------------------------------------
>
> Key: DERBY-3534
> URL: https://issues.apache.org/jira/browse/DERBY-3534
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
>
> It would be good to run the 10.3 tests against 10.4 to identify any compat issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3534) Run 10.3 tests against 10.4 to help
identify any compatibility issues
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578534#action_12578534 ]
Daniel John Debrunner commented on DERBY-3534:
----------------------------------------------
Any idea what test it failed on? Really the question is was it a server that had authentication enabled?
> Run 10.3 tests against 10.4 to help identify any compatibility issues
> ---------------------------------------------------------------------
>
> Key: DERBY-3534
> URL: https://issues.apache.org/jira/browse/DERBY-3534
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
>
> It would be good to run the 10.3 tests against 10.4 to identify any compat issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3534) Run 10.3 tests against 10.4 to help
identify any compatibility issues
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578573#action_12578573 ]
Daniel John Debrunner commented on DERBY-3534:
----------------------------------------------
> I ported most of change 632502 to my 10.3 client and hacked the server enough to get derbyTesting.jar to build and ran tests.
So were the initial results you posted were with this "hacking" or were they with an unaltered 10.3 derbyTesting.jar?
Just trying to understand the impact of the changes.
> Run 10.3 tests against 10.4 to help identify any compatibility issues
> ---------------------------------------------------------------------
>
> Key: DERBY-3534
> URL: https://issues.apache.org/jira/browse/DERBY-3534
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: rjall.out
>
>
> It would be good to run the 10.3 tests against 10.4 to identify any compat issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3534) Run 10.3 tests against 10.4 to help
identify any compatibility issues
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578511#action_12578511 ]
Kathey Marsden commented on DERBY-3534:
---------------------------------------
Well didn't get too far, got error shutting down network server and then
hung. I assume this is intended behavior related to DERBY-2109 .
I will look at what test changes need to be backported and see how
much further I get.
....................E.E.E.E.E.E.E.E.E.E.E.F.E.E.E.E.E.E.Ejava.sql.SQLException: Connection authentication failure occurr
ed. Reason: Invalid authentication..
at org.apache.derby.impl.drda.NetworkServerControlImpl.throwSQLException(NetworkServerControlImpl.java:3305)
at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessageWork(NetworkServerControlImpl.java:
3242)
at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessage(NetworkServerControlImpl.java:1862
)
at org.apache.derby.impl.drda.NetworkServerControlImpl.wrapSQLError(NetworkServerControlImpl.java:3820)
at org.apache.derby.impl.drda.NetworkServerControlImpl.readResult(NetworkServerControlImpl.java:2786)
at org.apache.derby.impl.drda.NetworkServerControlImpl.shutdown(NetworkServerControlImpl.java:1006)
at org.apache.derby.drda.NetworkServerControl.shutdown(NetworkServerControl.java:384)
at org.apache.derbyTesting.junit.NetworkServerTestSetup.tearDown(NetworkServerTestSetup.java:265)
at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at junit.textui.TestRunner.doRun(TestRunner.java:116)
at junit.textui.TestRunner.start(TestRunner.java:172)
at junit.textui.TestRunner.main(TestRunner.java:138)
.
> Run 10.3 tests against 10.4 to help identify any compatibility issues
> ---------------------------------------------------------------------
>
> Key: DERBY-3534
> URL: https://issues.apache.org/jira/browse/DERBY-3534
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
>
> It would be good to run the 10.3 tests against 10.4 to identify any compat issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3534) Run 10.3 tests against 10.4 to help
identify any compatibility issues
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3534:
----------------------------------
Attachment: 10.3.2.1_test_changes.txt
I created the branch https://svn.apache.org/repos/asf/db/derby/code/branches/10.3.2.1_test
to contain changes needed to run the 10.3.2.1 tests with 10.4 beta jars.
The only two changes that I am really concerned about from a user perspective are
------------------------------------------------------------------------
r638422 | kmarsden | 2008-03-18 08:51:22 -0700 (Tue, 18 Mar 2008) | 5 lines
Port test changes for DERBY-3160 (590720), to avoid authentication errors in
AuthenticationTest, PoolDSAuthenticationTest and XADSAuthenticationTest with
10.4
------------------------------------------------------------------------
r638155 | kmarsden | 2008-03-17 17:31:12 -0700 (Mon, 17 Mar 2008) | 4 lines
Portions of DERBY-2109 test changes (632502) for required user/password for
network server shutdown with authentication. Also put in stubs
for new NetworkServerControl commands.
------------------------------------------------------------------------
Neither of these issues have a release note at this time, but should. The full list of changes to get the tests running with IBM 1.6 are attached in the file 10.3.2.1_test_changes.txt. With these changes suites.All runs cleanly against 10.4 beta jars.
I am running derbyall to see if there is anything significant, but don't plan to make the changes on the branch to get derbyall to pass.
> Run 10.3 tests against 10.4 to help identify any compatibility issues
> ---------------------------------------------------------------------
>
> Key: DERBY-3534
> URL: https://issues.apache.org/jira/browse/DERBY-3534
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: 10.3.2.1_test_changes.txt, derby-3534_changes_for_running_tests_DO_NOT_COMMIT.txt, rjall.out
>
>
> It would be good to run the 10.3 tests against 10.4 to identify any compat issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3534) Run 10.3 tests against 10.4 to help
identify any compatibility issues
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3534:
----------------------------------
Attachment: rjall.out
rjall.out has 10.3 tests against 10.4 jars with most of change 632502 merged. Failures: 128, Errors: 76
Mostly its authentication failures and I think expected column Nullability changes. I will look more closely tomorrow,
> Run 10.3 tests against 10.4 to help identify any compatibility issues
> ---------------------------------------------------------------------
>
> Key: DERBY-3534
> URL: https://issues.apache.org/jira/browse/DERBY-3534
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: rjall.out
>
>
> It would be good to run the 10.3 tests against 10.4 to identify any compat issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (DERBY-3534) Run 10.3 tests against
10.4 to help identify any compatibility issues
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578577#action_12578577 ]
kmarsden edited comment on DERBY-3534 at 3/13/08 7:50 PM:
----------------------------------------------------------------
It would be helpful to have the release note for DERBY-2109 to understand the
scope of the behavior changes.
was (Author: kmarsden):
It would be helpful to have the release not for DERBY-2109 to understand the
scope of the behavior changes.
> Run 10.3 tests against 10.4 to help identify any compatibility issues
> ---------------------------------------------------------------------
>
> Key: DERBY-3534
> URL: https://issues.apache.org/jira/browse/DERBY-3534
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: derby-3534_changes_for_running_tests_DO_NOT_COMMIT.txt, rjall.out
>
>
> It would be good to run the 10.3 tests against 10.4 to identify any compat issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3534) Run 10.3 tests against 10.4 to help
identify any compatibility issues
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578577#action_12578577 ]
Kathey Marsden commented on DERBY-3534:
---------------------------------------
It would be helpful to have the release not for DERBY-2109 to understand the
scope of the behavior changes.
> Run 10.3 tests against 10.4 to help identify any compatibility issues
> ---------------------------------------------------------------------
>
> Key: DERBY-3534
> URL: https://issues.apache.org/jira/browse/DERBY-3534
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: derby-3534_changes_for_running_tests_DO_NOT_COMMIT.txt, rjall.out
>
>
> It would be good to run the 10.3 tests against 10.4 to identify any compat issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3534) Run 10.3 tests against 10.4 to help
identify any compatibility issues
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3534:
----------------------------------
Attachment: derbyall_report.txt
Attached is the report from the derbyall run. I think the store unit tests failed because my tests were built sane and I was running against insane jars. Nothing else caught my eye as particularly troublesome.
Kathey
> Run 10.3 tests against 10.4 to help identify any compatibility issues
> ---------------------------------------------------------------------
>
> Key: DERBY-3534
> URL: https://issues.apache.org/jira/browse/DERBY-3534
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: 10.3.2.1_test_changes.txt, derby-3534_changes_for_running_tests_DO_NOT_COMMIT.txt, derbyall_report.txt, rjall.out
>
>
> It would be good to run the 10.3 tests against 10.4 to identify any compat issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3534) Run 10.3 tests against 10.4 to help
identify any compatibility issues
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581588#action_12581588 ]
Kathey Marsden commented on DERBY-3534:
---------------------------------------
I ran suites.All with the following combinations:
I precreated the database system/wombat with 10.3 to test soft upgrade mode.
I filed issue DERBY-3566 related to this testing.
I tested the 10.3.2.1_test tests with 10.3.2.1 client 10.4 server and did not get any
interesting failures.
I tested the 10.3.2.1 tests with 10.4 client and 10.3.2.1 server and did not get any
interesting failures.
> Run 10.3 tests against 10.4 to help identify any compatibility issues
> ---------------------------------------------------------------------
>
> Key: DERBY-3534
> URL: https://issues.apache.org/jira/browse/DERBY-3534
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: 10.3.2.1_test_changes.txt, derby-3534_changes_for_running_tests_DO_NOT_COMMIT.txt, derbyall_report.txt, rjall.out
>
>
> It would be good to run the 10.3 tests against 10.4 to identify any compat issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3534) Run 10.3 tests against 10.4 to help
identify any compatibility issues
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578892#action_12578892 ]
Kathey Marsden commented on DERBY-3534:
---------------------------------------
Back to testing with the unchanged jars.
The test complaining about the authentication failure is SecureServerTest. which does have authentication enabled, but I noticed something strange. When I run the test it prints
the authentication error and hangs with the trace below printed to the console:
marsden@kmarsden-ln2:~/compattest/test> rju.ksh derbynet.SecureServerTest
..java.sql.SQLException: Connection authentication failure occurred. Reason: Invalid authentication..
at org.apache.derby.impl.drda.NetworkServerControlImpl.throwSQLException(NetworkServerControlImpl.java:3279)
at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessageWork(NetworkServerControlImpl.java:3216)
at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessage(NetworkServerControlImpl.java:1836)
at org.apache.derby.impl.drda.NetworkServerControlImpl.wrapSQLError(NetworkServerControlImpl.java:3794)
at org.apache.derby.impl.drda.NetworkServerControlImpl.readResult(NetworkServerControlImpl.java:2760)
at org.apache.derby.impl.drda.NetworkServerControlImpl.shutdown(NetworkServerControlImpl.java:1005)
at org.apache.derby.drda.NetworkServerControl.shutdown(NetworkServerControl.java:384)
at org.apache.derbyTesting.junit.NetworkServerTestSetup.tearDown(NetworkServerTestSetup.java:265)
at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at junit.textui.TestRunner.doRun(TestRunner.java:116)
at junit.textui.TestRunner.start(TestRunner.java:172)
at junit.textui.TestRunner.main(TestRunner.java:138)
I then tried to bring the server down manually with:
kmarsden@kmarsden-ln2:~/compattest> java org.apache.derby.drda.NetworkServerControl shutdown -user MARY -password marypwd
It tells me happily that my server is down, but that's not true. My test is still hung and if I print a stack dump I see that my network server is still started. I can ping it as well.
I think there is a bug here. Perhaps I need to have permissions in my policy file, but
regardless it shouldn't have told me my server was down when it wasn't. I'll try to get
a repro outside the harness.
> Run 10.3 tests against 10.4 to help identify any compatibility issues
> ---------------------------------------------------------------------
>
> Key: DERBY-3534
> URL: https://issues.apache.org/jira/browse/DERBY-3534
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: derby-3534_changes_for_running_tests_DO_NOT_COMMIT.txt, rjall.out
>
>
> It would be good to run the 10.3 tests against 10.4 to identify any compat issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3534) Run 10.3 tests against 10.4 to help
identify any compatibility issues
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3534:
----------------------------------
Attachment: derby-3534_changes_for_running_tests_DO_NOT_COMMIT.txt
The results are after merging the test changes and hacking my 10.3 server so the test changes would compile. Only derbyTesting.jar was used from 10.3, not the hacked server changes, those were just so I could compile.
I will back up tomorrow and get a better understanding of what was happening without the changes as well as analyze these failures.
I am attaching my 10.3 diffs (derby-3534_changes_for_running_tests_DO_NOT_COMMIT.txt( just for reference. The server is totally broken so absolutely NOT FOR COMMIT.
> Run 10.3 tests against 10.4 to help identify any compatibility issues
> ---------------------------------------------------------------------
>
> Key: DERBY-3534
> URL: https://issues.apache.org/jira/browse/DERBY-3534
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: derby-3534_changes_for_running_tests_DO_NOT_COMMIT.txt, rjall.out
>
>
> It would be good to run the 10.3 tests against 10.4 to identify any compat issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-3534) Run 10.3 tests against 10.4 to help
identify any compatibility issues
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden closed DERBY-3534.
---------------------------------
Resolution: Fixed
Fix Version/s: 10.4.0.0
Completed this testing. Only issues Identified were:
DERBY-2109 needs release note and doc updates. Martin is working on this.
DERBY-3160 needs a release note. Don't think anyone is working on this.
Created: (DERBY-3566) Alter column set data type not allowed in soft upgrade with unique constraint
The 10.3.2.1_test branch now runs cleanly against 10.4
> Run 10.3 tests against 10.4 to help identify any compatibility issues
> ---------------------------------------------------------------------
>
> Key: DERBY-3534
> URL: https://issues.apache.org/jira/browse/DERBY-3534
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Fix For: 10.4.0.0
>
> Attachments: 10.3.2.1_test_changes.txt, derby-3534_changes_for_running_tests_DO_NOT_COMMIT.txt, derbyall_report.txt, rjall.out
>
>
> It would be good to run the 10.3 tests against 10.4 to identify any compat issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3534) Run 10.3 tests against 10.4 to help
identify any compatibility issues
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578559#action_12578559 ]
Daniel John Debrunner commented on DERBY-3534:
----------------------------------------------
Thanks for doing this Kathey, actually "playing" with the software to discover (or in this case see the actual effects of a known change) possible issues is much more effective than trying to discern them from a spec, code review or mailing list discussion. That's the benefit of applying patches (the ability for others to get their hands dirty with the code), the downside is possible leaving the codeline in a less than perfect state, especially if there's no followup from anyone.
> Run 10.3 tests against 10.4 to help identify any compatibility issues
> ---------------------------------------------------------------------
>
> Key: DERBY-3534
> URL: https://issues.apache.org/jira/browse/DERBY-3534
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: rjall.out
>
>
> It would be good to run the 10.3 tests against 10.4 to identify any compat issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.