At the same time there are tests that reside in exclude lists by absolutely unknown reason. I.e. initially they were added because of some issue that was fixed a quarter ago. So IMHO the only way to get rid of such unwanted excludes is to run *all* tests periodically and check do they fail anymore. This is an exhausting work - thanks Tatyana for doing this. BTW I think it will be also nice if we put JIRA number or any other useful comment directly to exclude lists just as a reminder why this test is here.
Thanks, 2007/2/19, Mikhail Loenko <[EMAIL PROTECTED]>:
It would be good to find what were the reasons for excluding those 12 tests. For example, the first test in the patch: org/apache/harmony/auth/tests/module/Krb5LoginModuleTest.java was originally excluded in build.xml with the following comment: <!-- The test is under development --> <!-- excluded to avoid random failures --> Since that the code of the test was not modified, so the test is still incomplete and should not be returned back. Other tests may have similar problems too Thanks, Mikhail 2007/2/19, tatyana doubtsova <[EMAIL PROTECTED]>: > Hi, > I've run excluded classlib tests on win ia32 drlvm|ibmvme, linux ia32 > drlvm|ibmvme, linux em64t drlvm and found out that 12 tests from common > x-lists passed on all 5 configurations. The tests are from auth, luni, > nio_char, rmi, sound, text, lang-manegement, and security modules. I've > prepared the patch for x-lists clean-up: > https://issues.apache.org/jira/browse/HARMONY-3194. Commiters, would you, > please, have a look and apply, if there are no objections? > > Thanks, > Tanya
-- Alexei Zakharov, Intel ESSD
