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.