[
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.
