a simple test report for PharoCore 1.1 is now automatically published at
http://pharo.gforge.inria.fr/experimental/ what do you think? I would propose to remove the google wiki test entries (for 1.1) and point them here. cheers, Mike _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
While we're at it, a nice addition to this would be to identify the platform (Win, Mac, Linux, etc...). Sometimes, you get surprises on some platforms... :) Benoit St-Jean Yahoo! Messenger: bstjean Blog: lamneth.wordpress.com A standpoint is an intellectual horizon of radius zero. (Albert Einstein) From: Michael Roberts <[hidden email]> To: Pharo-project <[hidden email]> Sent: Thu, January 7, 2010 5:36:11 PM Subject: [Pharo-project] Interim build server update a simple test report for PharoCore 1.1 is now automatically published at http://pharo.gforge.inria.fr/experimental/ what do you think? I would propose to remove the google wiki test entries (for 1.1) and point them here. cheers, Mike _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project Looking for the perfect gift? Give the gift of Flickr! _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Michael Roberts-2
On Thu, Jan 7, 2010 at 11:36 PM, Michael Roberts <[hidden email]> wrote: a simple test report for PharoCore 1.1 is now automatically published at 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
_______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Michael Roberts-2
On Jan 7, 2010, at 11:36 PM, Michael Roberts wrote: > a simple test report for PharoCore 1.1 is now automatically published at > > http://pharo.gforge.inria.fr/experimental/ > > what do you think? I love the term automatically it sounds like faery :) > > I would propose to remove the google wiki test entries (for 1.1) and > point them here. yes > > cheers, > Mike > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] 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 _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Michael Roberts-2
On 7 janv. 2010, at 23:36, Michael Roberts wrote: > a simple test report for PharoCore 1.1 is now automatically published at > > http://pharo.gforge.inria.fr/experimental/ > > what do you think? > Sounds good (cant say 'looks', it's a bit crude on the look-likability :)) What is the next step? Hudson integration, test history, visualization? -- Simon _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Mariano Martinez Peck
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 > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
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 <[hidden email]> 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 [hidden email] 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 > <[hidden email]> 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 > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Free forum by Nabble | Edit this page |