Mauve reports

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://developer.classpath.org/pipermail/classpath/attachments/20060609/527da4db/attachment.pgp

[Index of Archives]     [Linux Kernel]     [Linux Cryptography]     [Fedora]     [Fedora Directory]     [Red Hat Development]

  Powered by Linux