Re: Mauve reports
Hi everyone, sorry I was away for a few days until yesterday. Roman this is great, thanks a lot. Somebody asked about changing the timeout value, if the script is using the old harness I don't think that's possible but if we change the scripts to use the new stuff the command to run all the tests with a custom timeout value would be "$(JAVA) Harness -timeout X" David I'll investigate why some tests aren't running. Cheers all, Tony On Thu, 2006-06-08 at 08:57 -0600, Tom Tromey wrote: > > "Roman" == Roman Kennke <[EMAIL PROTECTED]> writes: > > Roman> FYI: I have set up my old Mauve report script on builder.classpath.org > Roman> to generate nice HTML for the Mauve results: > > Thanks! > > Roman> http://builder.classpath.org/mauve/mauvereport.cgi > > I made a link to this from the builder's main web page. > > Tom >
Re: Mauve reports
Roman Kennke wrote: I'd like to get JCHEVM (the Harmony edition of JCVM) included.. is that possible? Let me know what I can do to help if so. This should be possible. Whenever me or Mark or somebody else finds time to fiddle with the build scripts we will include this. OTOH, it might be possible that Mark gives you access to the machine so you can set this up yourself? That'd be fine with me... just let me know what I need to do. Thanks, -Archie __ Archie Cobbs *CTO, Awarix* http://www.awarix.com
Re: Mauve reports
hello Roman, On Friday 09 June 2006 00:13, Roman Kennke wrote: > FYI: I have set up my old Mauve report script on > builder.classpath.org to generate nice HTML for the Mauve results: > > http://builder.classpath.org/mauve/mauvereport.cgi very useful. thanks for doing this. > This really is only a frontend to: > http://builder.classpath.org/mauve/mauve-jamvm > > These results normally get updated continuously, so the frontend > should always report the latest results that have been built > sucessfully. > > In the future we will (hopefully) add more compiler/VM(/classlib) > combinations so that we can compare the results to others. > > I welcome suggestions for improvements of this frontend. * it wasn't clear to me if the Last update date, is local or UTC. * what timeout value is used in the scripts? i see that most of the failed tests are due to timeout. since this is an automated build/test process, may be we can increase that limit. cheers; rsn pgpnWc66a6X6C.pgp Description: PGP signature
Re: Mauve reports
Bryce McKinlay wrote: Roman Kennke wrote: Also, the ability to see/track when a failure started occurring could be very useful. That way we could easily match up new failures with patches that caused them. Hmm, that's an interesting feature indeed. We would have to keep diffs between versions around and teach the script to parse and display them somehow. I must think about this a little. It should become a bit easier with the new test harness. When you treat 1 test = 1 failure, each pass/fail can be uniquely identified, and regressions can be distinguished easily from new test cases. Yes, I posted a patch that makes the new harness the default and removes the old one to [EMAIL PROTECTED] yesterday. No one has responded thus far, but I'd appreciate comments. Tom
Re: Mauve reports
Roman Kennke wrote: Also, the ability to see/track when a failure started occurring could be very useful. That way we could easily match up new failures with patches that caused them. Hmm, that's an interesting feature indeed. We would have to keep diffs between versions around and teach the script to parse and display them somehow. I must think about this a little. It should become a bit easier with the new test harness. When you treat 1 test = 1 failure, each pass/fail can be uniquely identified, and regressions can be distinguished easily from new test cases. Bryce
Re: Mauve reports
On Fri, 2006-06-09 at 00:02 +0200, Roman Kennke wrote:
> Hi Andrew,
>
> Am Donnerstag, den 08.06.2006, 22:01 +0100 schrieb Andrew John Hughes:
> > On Thu, 2006-06-08 at 16:13 +0200, Roman Kennke wrote:
> > > FYI: I have set up my old Mauve report script on builder.classpath.org
> > > to generate nice HTML for the Mauve results:
> > >
> > > http://builder.classpath.org/mauve/mauvereport.cgi
> > >
> > > This really is only a frontend to:
> > > http://builder.classpath.org/mauve/mauve-jamvm
> > >
> > > These results normally get updated continuously, so the frontend should
> > > always report the latest results that have been built sucessfully.
> > >
> > > In the future we will (hopefully) add more compiler/VM(/classlib)
> > > combinations so that we can compare the results to others.
> > >
> > > I welcome suggestions for improvements of this frontend.
> > >
> > > /Roman
> > >
> >
> > Great work; I wondered what had happened to these.
>
> :-) This was actually one of my first contributions to Classpath when I
> started. Then they got lost somehow, with the plan to setup on builder,
> what never happened - until now.
>
> > But should I only be seeing gcj+jamvm?
>
> Of course not. But atm builder only generates mauve reports for this
> setup. We really should add more compilers/VMs soon... Any help with
> this is greatly appreciated.
>
> /Roman
>
Yes, but with three different variations: old release, HEAD and future
release (although the latter is obviously turned off at present). I
don't know which your page is showing, but there are currently two
active sets of Mauve results.
Cheers,
--
Andrew :-)
Please avoid sending me Microsoft Office (e.g. Word, PowerPoint)
attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
If you use Microsoft Office, support movement towards the end of vendor
lock-in:
http://opendocumentfellowship.org/petition/
"Value your freedom, or you will lose it, teaches history.
`Don't bother us with politics' respond those who don't want to learn."
-- Richard Stallman
Escape the Java Trap with GNU Classpath!
http://www.gnu.org/philosophy/java-trap.html
public class gcj extends Freedom implements Java { ... }
signature.asc
Description: This is a digitally signed message part
Re: Mauve reports
> "Roman" == Roman Kennke <[EMAIL PROTECTED]> writes: Roman> Hmm, that's an interesting feature indeed. We would have to keep diffs Roman> between versions around and teach the script to parse and display them Roman> somehow. I must think about this a little. We've already got a script to do this for some cases. That is how we mail out regression reports. Tom
Re: Mauve reports
Hi Bryce, Am Donnerstag, den 08.06.2006, 16:38 -0400 schrieb Bryce McKinlay: > Roman Kennke wrote: > > These results normally get updated continuously, so the frontend should > > always report the latest results that have been built sucessfully. > > > > In the future we will (hopefully) add more compiler/VM(/classlib) > > combinations so that we can compare the results to others. > > > > I welcome suggestions for improvements of this frontend. > > > > Sweet! I think it may be more useful to only report the failures. > Scrolling through the many thousands of PASSes isn't really very > interesting :) Yeah, this should be easily implemented. > Also, the ability to see/track when a failure started occurring could be > very useful. That way we could easily match up new failures with patches > that caused them. Hmm, that's an interesting feature indeed. We would have to keep diffs between versions around and teach the script to parse and display them somehow. I must think about this a little. /Roman -- “Improvement makes straight roads, but the crooked roads, without Improvement, are roads of Genius.” - William Blake signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: Mauve reports
Hi Andrew, Am Donnerstag, den 08.06.2006, 22:01 +0100 schrieb Andrew John Hughes: > On Thu, 2006-06-08 at 16:13 +0200, Roman Kennke wrote: > > FYI: I have set up my old Mauve report script on builder.classpath.org > > to generate nice HTML for the Mauve results: > > > > http://builder.classpath.org/mauve/mauvereport.cgi > > > > This really is only a frontend to: > > http://builder.classpath.org/mauve/mauve-jamvm > > > > These results normally get updated continuously, so the frontend should > > always report the latest results that have been built sucessfully. > > > > In the future we will (hopefully) add more compiler/VM(/classlib) > > combinations so that we can compare the results to others. > > > > I welcome suggestions for improvements of this frontend. > > > > /Roman > > > > Great work; I wondered what had happened to these. :-) This was actually one of my first contributions to Classpath when I started. Then they got lost somehow, with the plan to setup on builder, what never happened - until now. > But should I only be seeing gcj+jamvm? Of course not. But atm builder only generates mauve reports for this setup. We really should add more compilers/VMs soon... Any help with this is greatly appreciated. /Roman -- “Improvement makes straight roads, but the crooked roads, without Improvement, are roads of Genius.” - William Blake signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: Mauve reports
Hi Archie, Am Donnerstag, den 08.06.2006, 11:55 -0500 schrieb Archie Cobbs: > David Gilbert wrote: > > Roman Kennke wrote: > >> These results normally get updated continuously, so the frontend should > >> always report the latest results that have been built sucessfully. > >> > >> In the future we will (hopefully) add more compiler/VM(/classlib) > >> combinations so that we can compare the results to others. > > I'd like to get JCHEVM (the Harmony edition of JCVM) included.. > is that possible? Let me know what I can do to help if so. This should be possible. Whenever me or Mark or somebody else finds time to fiddle with the build scripts we will include this. OTOH, it might be possible that Mark gives you access to the machine so you can set this up yourself? /Roman -- “Improvement makes straight roads, but the crooked roads, without Improvement, are roads of Genius.” - William Blake signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: Mauve reports
On Thu, 2006-06-08 at 16:13 +0200, Roman Kennke wrote:
> FYI: I have set up my old Mauve report script on builder.classpath.org
> to generate nice HTML for the Mauve results:
>
> http://builder.classpath.org/mauve/mauvereport.cgi
>
> This really is only a frontend to:
> http://builder.classpath.org/mauve/mauve-jamvm
>
> These results normally get updated continuously, so the frontend should
> always report the latest results that have been built sucessfully.
>
> In the future we will (hopefully) add more compiler/VM(/classlib)
> combinations so that we can compare the results to others.
>
> I welcome suggestions for improvements of this frontend.
>
> /Roman
>
Great work; I wondered what had happened to these.
But should I only be seeing gcj+jamvm?
Cheers,
--
Andrew :-)
Please avoid sending me Microsoft Office (e.g. Word, PowerPoint)
attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
If you use Microsoft Office, support movement towards the end of vendor
lock-in:
http://opendocumentfellowship.org/petition/
"Value your freedom, or you will lose it, teaches history.
`Don't bother us with politics' respond those who don't want to learn."
-- Richard Stallman
Escape the Java Trap with GNU Classpath!
http://www.gnu.org/philosophy/java-trap.html
public class gcj extends Freedom implements Java { ... }
signature.asc
Description: This is a digitally signed message part
Re: Mauve reports
Roman Kennke wrote: These results normally get updated continuously, so the frontend should always report the latest results that have been built sucessfully. In the future we will (hopefully) add more compiler/VM(/classlib) combinations so that we can compare the results to others. I welcome suggestions for improvements of this frontend. Sweet! I think it may be more useful to only report the failures. Scrolling through the many thousands of PASSes isn't really very interesting :) Also, the ability to see/track when a failure started occurring could be very useful. That way we could easily match up new failures with patches that caused them. Bryce
Re: Mauve reports
David Gilbert wrote: Roman Kennke wrote: These results normally get updated continuously, so the frontend should always report the latest results that have been built sucessfully. In the future we will (hopefully) add more compiler/VM(/classlib) combinations so that we can compare the results to others. I'd like to get JCHEVM (the Harmony edition of JCVM) included.. is that possible? Let me know what I can do to help if so. Some details... - It's easy to download the latest source, but you'll need an SVN client - The SVN build requires the usual autofoo stuff (automake, autoconf, etc). There is a script included that runs everything (including ./configure). - Still targeted at Classpath 0.90, due to the fatal bug in Classpath 0.91 that makes startup fail with a NullPointerException. I have a patch for 0.91 though (it's currently checked in as an unapplied patch). Thanks, -Archie __ Archie Cobbs *CTO, Awarix* http://www.awarix.com
Re: Mauve reports
Roman Kennke wrote: FYI: I have set up my old Mauve report script on builder.classpath.org to generate nice HTML for the Mauve results: http://builder.classpath.org/mauve/mauvereport.cgi Nice! This really is only a frontend to: http://builder.classpath.org/mauve/mauve-jamvm Does anyone know why some tests don't appear in there (for example, tests for the MetalLookAndFeel class)? These results normally get updated continuously, so the frontend should always report the latest results that have been built sucessfully. In the future we will (hopefully) add more compiler/VM(/classlib) combinations so that we can compare the results to others. I welcome suggestions for improvements of this frontend. /Roman Can someone update the GNU Classpath home page to point to this report, instead of the one that I run manually (which is the current link on the home page)? Regards, Dave
Re: Mauve reports
> "Roman" == Roman Kennke <[EMAIL PROTECTED]> writes: Roman> FYI: I have set up my old Mauve report script on builder.classpath.org Roman> to generate nice HTML for the Mauve results: Thanks! Roman> http://builder.classpath.org/mauve/mauvereport.cgi I made a link to this from the builder's main web page. Tom
Mauve reports
FYI: I have set up my old Mauve report script on builder.classpath.org to generate nice HTML for the Mauve results: http://builder.classpath.org/mauve/mauvereport.cgi This really is only a frontend to: http://builder.classpath.org/mauve/mauve-jamvm These results normally get updated continuously, so the frontend should always report the latest results that have been built sucessfully. In the future we will (hopefully) add more compiler/VM(/classlib) combinations so that we can compare the results to others. I welcome suggestions for improvements of this frontend. /Roman -- “Improvement makes straight roads, but the crooked roads, without Improvement, are roads of Genius.” - William Blake signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Mauve reports
I updated the Mauve test report: http://www.object-refinery.com/classpath/mauve/report/ ...and the StatCVS report for Mauve: http://www.object-refinery.com/classpath/mauve/statcvs/ Regards, Dave ___ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
Re: automated mauve reports
Robert Schuster wrote: > Hi list, > tell me if I am wrong but in gnu.testlet.java.lang.Byte lines like this > occur: > | > PASS: gnu.testlet.java.lang.Byte.ByteTest: Error : test_decode failed - > 2 (number 1)| > > Isn't that (and many others) a failed test? No... you are looking at verbose output which shows the failure message that would have been displayed had the test failed.. -Archie __ Archie Cobbs *CTO, Awarix* http://www.awarix.com ___ Classpath mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/classpath
Re: automated mauve reports
Hi list, tell me if I am wrong but in gnu.testlet.java.lang.Byte lines like this occur: PASS: gnu.testlet.java.lang.Byte.ByteTest: Error : test_decode failed - 2 (number 1) Isn't that (and many others) a failed test? cu Robert C. Brian Jones wrote: On Sun, 2004-07-18 at 12:32, Roman Kennke wrote: Am So, den 18.07.2004 schrieb Mark Wielaard um 16:36: Hi Roman, On Sun, 2004-07-18 at 00:23, Roman Kennke wrote: http://ontographics.com/classpath/report-index.html I still have to improve the script. When it is perfect, I will make a cron job out of it, which will fetch the current cvs of mauve and classpath and generate these reports on a nightly basis. Wow! Very useful! Would it be hard to adapt your script so it reports the number of passes/fails for each level? e.g something like: dir PASS FAIL awt 603 123 beans 78 8 io 120 67 Yes, that should be no problem. I will modifiy the script, so that it generates the HTML on the fly, which enables additional options, like filtering FAIL/PASS and maybe some more. BTW. The original japhar had a mauve parsing script which is now also used by kaffe: http://www.kaffe.org/cgi-bin/viewcvs.cgi/*checkout*/kaffe/developers/mauve-html-gen.pl?rev=HEAD Why is this script not in action? /Roman You may find something useful from these scripts as well, see http://www.haphazard.org/~cbj/classpath/automauve-1.0.tar.gz. I like how what you've done is starting towards that consolidated japi/mauve view I mentioned a couple of weeks ago. Brian ___ Classpath mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/classpath
Re: automated mauve reports
On Sun, 2004-07-18 at 12:32, Roman Kennke wrote: > Am So, den 18.07.2004 schrieb Mark Wielaard um 16:36: > > Hi Roman, > > > > On Sun, 2004-07-18 at 00:23, Roman Kennke wrote: > > > http://ontographics.com/classpath/report-index.html > > > > > > I still have to improve the script. When it is perfect, I will make a > > > cron job out of it, which will fetch the current cvs of mauve and > > > classpath and generate these reports on a nightly basis. > > > > Wow! Very useful! > > Would it be hard to adapt your script so it reports the number of > > passes/fails for each level? e.g something like: > > > > dir PASSFAIL > > > > awt 603 123 > > beans78 8 > > io 120 67 > > Yes, that should be no problem. I will modifiy the script, so that it > generates the HTML on the fly, which enables additional options, like > filtering FAIL/PASS and maybe some more. > > > > BTW. The original japhar had a mauve parsing script which is now also > > used by kaffe: > > http://www.kaffe.org/cgi-bin/viewcvs.cgi/*checkout*/kaffe/developers/mauve-html-gen.pl?rev=HEAD > > > Why is this script not in action? > > /Roman > You may find something useful from these scripts as well, see http://www.haphazard.org/~cbj/classpath/automauve-1.0.tar.gz. I like how what you've done is starting towards that consolidated japi/mauve view I mentioned a couple of weeks ago. Brian -- Brian Jones <[EMAIL PROTECTED]> ___ Classpath mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/classpath
Re: automated mauve reports
Am So, den 18.07.2004 schrieb Mark Wielaard um 16:36: > Hi Roman, > > On Sun, 2004-07-18 at 00:23, Roman Kennke wrote: > > http://ontographics.com/classpath/report-index.html > > > > I still have to improve the script. When it is perfect, I will make a > > cron job out of it, which will fetch the current cvs of mauve and > > classpath and generate these reports on a nightly basis. > > Wow! Very useful! > Would it be hard to adapt your script so it reports the number of > passes/fails for each level? e.g something like: > > dir PASSFAIL > > awt 603 123 > beans 78 8 > io120 67 Ok, added. I also have added a cron job, which updates these pages nightly with current CVS of both Classpath and Mauve. The script now generates the HTML pages on the fly from the mauve output and is at a new location: http://ontographics.com/classpath/mauve/mauvereport.cgi The next thing I will do is to add more compilers and VMs and build in a switch in each page to select a compiler/VM combo. Cheers, Roman signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Classpath mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/classpath
Re: automated mauve reports
Am So, den 18.07.2004 schrieb Mark Wielaard um 16:36: > Hi Roman, > > On Sun, 2004-07-18 at 00:23, Roman Kennke wrote: > > http://ontographics.com/classpath/report-index.html > > > > I still have to improve the script. When it is perfect, I will make a > > cron job out of it, which will fetch the current cvs of mauve and > > classpath and generate these reports on a nightly basis. > > Wow! Very useful! > Would it be hard to adapt your script so it reports the number of > passes/fails for each level? e.g something like: > > dir PASSFAIL > > awt 603 123 > beans 78 8 > io120 67 Yes, that should be no problem. I will modifiy the script, so that it generates the HTML on the fly, which enables additional options, like filtering FAIL/PASS and maybe some more. > BTW. The original japhar had a mauve parsing script which is now also > used by kaffe: > http://www.kaffe.org/cgi-bin/viewcvs.cgi/*checkout*/kaffe/developers/mauve-html-gen.pl?rev=HEAD Why is this script not in action? /Roman signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Classpath mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/classpath
Re: automated mauve reports
Hi Roman, On Sun, 2004-07-18 at 00:23, Roman Kennke wrote: > http://ontographics.com/classpath/report-index.html > > I still have to improve the script. When it is perfect, I will make a > cron job out of it, which will fetch the current cvs of mauve and > classpath and generate these reports on a nightly basis. Wow! Very useful! Would it be hard to adapt your script so it reports the number of passes/fails for each level? e.g something like: dir PASSFAIL awt 603 123 beans78 8 io 120 67 BTW. The original japhar had a mauve parsing script which is now also used by kaffe: http://www.kaffe.org/cgi-bin/viewcvs.cgi/*checkout*/kaffe/developers/mauve-html-gen.pl?rev=HEAD Cheers, Mark signature.asc Description: This is a digitally signed message part ___ Classpath mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/classpath
automated mauve reports
Hi list, in order to improve my efforts in testing for compatibility and completeness (http://ontographics.com/classpath/status-1.0.html), I have written a nice script, which takes mauve output files as input and transforms them into html pages like these: http://ontographics.com/classpath/report-index.html I still have to improve the script. When it is perfect, I will make a cron job out of it, which will fetch the current cvs of mauve and classpath and generate these reports on a nightly basis. Have fun, Roman signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Classpath mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/classpath
