<>Hm. Actually, I am wondering if we should not also save the
derbyTesting.jar at the same release level.

<>Daniel John Debrunner wrote:

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.

From last email:

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?

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 have now changed the testing.txt file into a .html, and added a table to show the tests I know were run at IBM. Other folks could/should add their test results to it.
If this file looks good, it should get checked in next to the derbyTesting.jar of build 106978 parallel to the incubator release...


Myrna

Title: readme.htm




derbyTesting notes re derby 10.0.2.1 (build 106978)


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

Note: the issue of derby-77 indicates that one needs to have derbyLocale_*.jar in the classpath or 1 test (derbynet/sysinfo) will fail.

The derbyall suite of this build has one failure; the test lang/UnitTests.java cannot be found. This will show up in the summary file derbyall.sum, and as 1 failed test in derbyall_report.txt.

The following tests were executed successfully:

Type test
platform, jvm version
by.:
 SUN J2EE complience test
         jdbc suite (version 141);
         xa suite (version 141 plus patch)
OS: WIN 2000. jvm: Sun jdk 142.
[EMAIL PROTECTED]
org.apache.derbyTesting.
    functionTests.suites.derbyall
WIN 2000/ibm142,
WIN 2000/jdk142
[EMAIL PROTECTED]
Cloudscape functional Tests yet to be contributed to apache
WIN 2000/ibm142,
WIN 2000/jdk142
[EMAIL PROTECTED]





Reply via email to