Re: [cp-patches] FYI: Update mauve results link: Not all tests run.

[David Gilbert]

Meskauskas Audrius wrote:

> Generally, very nice. 
> http://www.object-refinery.com/classpath/mauve/report/, however, 
> contains several strange places where it would be great to have more 
> details in order to correct the test or Classpath problems.
>
> 1. There are 3 test for javax.swing.timer and none is mentioned in 
> report. They run as Mauve tests for me. If anybody has an idea why 
> they did not run, please inform me that I could correct.

Two of the tests are reported here:

http://www.object-refinery.com/classpath/mauve/report/javax/swing/Timer/class_index.html

The other one was committed to CVS after I ran that report (on Sept 12).

> 2. A whole set of  tests did not run due "Class not found". It is very 
> difficult to figure out that is going wrong without knowing which 
> class it was. Tests in gnu.testlet.gnu.javax.swing.text.html.parser.* 
> were all checked before committing them to Mauve. It you give me the 
> stack traces, I will correct the problem.

The "Class not found" refers to the test class not being found, because 
I put a "//" in front of it in the 'tests.txt' file.  I commented out 
the gnu.javax.swing.text.html.parser.* tests because I also ran the same 
set of tests against the JDK for comparison purposes.

Some of the other tests I commented out because they caused the test run 
to crash or hang (using JamVM).  I didn't spend any time investigating 
these problems, but if anyone wants to, the report generator is in Mauve 
CVS in the gnu.testlet.runner.* package.  I just sent Mark a link to the 
report, because I thought it would be an improvement on the currently 
broken link on the Classpath home page.  I've no doubt someone can 
improve on my improvement - for instance, automating the process to have 
it run every night would be great.  I'm allergic to automation scripts, 
so I'll let someone else do that...

Regards,

Dave Gilbert