Now that the log file on failure is appened to the previous log I think that we should pay attention or explicitly have the possibility to write a fresh one. Because we can have a problem: I got some 5 mb log file. Stef

a simple test report for PharoCore 1.1 is now automatically published at

http://pharo.gforge.inria.fr/experimental/

what do you think?

That's really cool!!! I cannot image what good this will be together with Hudson!!!

I am agree with the OS. Some tests use to be ok for one platform but not in another one (I don't remember right now). Even more, I would print the VM also. Maybe you can put all that information that it is put at the beginning of the PharoDebug.log. I remember there was a way to get that information....but I don't remember how hahaha.

EXCELLENT!

Cheers

Mariano

I would propose to remove the google wiki test entries (for 1.1) and point them here.

cheers, Mike

_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

yeap I'm quite good at integrating fixes that break tests :) Stef On Jan 8, 2010, at 9:10 PM, Michael Roberts wrote:

Simon thanks for looking.

next steps: -bullet proof it -export error log files -hudson -host on community server -developers use results to FIX BUGS QUICKLY

nice to have: -certainly a fancy history web interface -stats, etc

however i must shout about fixing bugs, because surely the most beautiful test result page is one that is blank! seriously, we need as a community to get new bugs fixed early. to me that is the whole point.

thanks, Mike

On Fri, Jan 8, 2010 at 1:25 PM, Stéphane Ducasse <Stephane.Ducasse@inria.fr> wrote:

...

Now that the log file on failure is appened to the previous log I think that we should pay attention or explicitly have the possibility to write a fresh one. Because we can have a problem: I got some 5 mb log file.

Stef - yes, next I am integrating a specific error file per build report. should solve the problem. we will have to see in practice.

_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

good points, i will get more OS information into it. Realistically we will probably only run these on Linux, but if we really cared we could find a windows server (or pay on Amazon EC2) and report for multiple OS. We would need a Windows admin to volunteer ;-) cheers, Mike