Daniel John Debrunner wrote:
myrnap wrote:I build the derbyTesting.jar for 106978 revision. It should be placed at the same level as the lib and bin downloads. Should I send it to the list or can I send it to one of the committers directly?
Hm. Actually, I am wondering if we should not also save the
derbyTesting.jar at the same release level.
Agreed, and a list on the site of which jvm/os/hardware combinations people have run with the Derby tests would be useful. That is if anyone runs the tests they could report the results to one of the lists and then subsequently it could be summarized on the site.
I have attached a testing release notes/readme file that should probably go in the new branch?
It should go with the derbyTesting.jar.
It lists the testing bugs, it could also function as the place to list tested revisions. If people sent their testing efforts to the list I'll be happy to combine it, or else maybe this file can just be patched?
I put the cts test suite results that I already sent to the list in it.
If someone could commit these to svn...
Thx, Myrna
This file is to accompany the derbyTesting.jar for the derby incubator release 10.0.2.1, build 106978.
The following known issues were documented in the JIRA bug tracking system for tests on the day of the release: Key Summary DERBY-77 Test instructions incomplete for setting classpath. DERBY-88 RunSuite summary rounds incorrectly The following tests were executed successfully: - Sun J2EE Complience Test Suite (version 141) jdbc and xa suites (OS: Win 2000)
