[Pharo-project] How to see failures/erros of the Hudson server?
I know we have just started with the Hudson server, but is there a way to see why a test is failing/error ? For the errors, at least we can see the PharoDebug.log ? THe other idea we have today (talking with Marcus) is to have RFB running in the hudson images. So that we can connect and browse it. Of course, it could be password protected so that not everybody can do it. What do you think? Cheers Mariano
Failing tests: http://hudson.lukas-renggli.ch/job/Pharo/lastCompletedBuild/testReport/ http://hudson.lukas-renggli.ch/job/Pharo/lastCompletedBuild/testReport/Tests... log: http://hudson.lukas-renggli.ch/job/Pier/64/console 2010/7/20 Mariano Martinez Peck <marianopeck@gmail.com>
I know we have just started with the Hudson server, but is there a way to see why a test is failing/error ? For the errors, at least we can see the PharoDebug.log ? THe other idea we have today (talking with Marcus) is to have RFB running in the hudson images. So that we can connect and browse it. Of course, it could be password protected so that not everybody can do it.
What do you think?
Cheers
Mariano
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
As Nick points out. Additionally, the image with the tests is saves so you can download and run it. Lukas 2010/7/20 Nick Ager <nick.ager@gmail.com>:
Failing tests: http://hudson.lukas-renggli.ch/job/Pharo/lastCompletedBuild/testReport/ http://hudson.lukas-renggli.ch/job/Pharo/lastCompletedBuild/testReport/Tests... log: http://hudson.lukas-renggli.ch/job/Pier/64/console
2010/7/20 Mariano Martinez Peck <marianopeck@gmail.com>
I know we have just started with the Hudson server, but is there a way to see why a test is failing/error ? For the errors, at least we can see the PharoDebug.log ? THe other idea we have today (talking with Marcus) is to have RFB running in the hudson images. So that we can connect and browse it. Of course, it could be password protected so that not everybody can do it.
What do you think?
Cheers
Mariano
_______________________________________________ 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
-- Lukas Renggli www.lukas-renggli.ch
this is cool :) thank you very much mariano On Tue, Jul 20, 2010 at 3:49 PM, Lukas Renggli <renggli@gmail.com> wrote:
As Nick points out. Additionally, the image with the tests is saves so you can download and run it.
Lukas
2010/7/20 Nick Ager <nick.ager@gmail.com>:
Failing tests: http://hudson.lukas-renggli.ch/job/Pharo/lastCompletedBuild/testReport/
http://hudson.lukas-renggli.ch/job/Pharo/lastCompletedBuild/testReport/Tests...
log: http://hudson.lukas-renggli.ch/job/Pier/64/console
2010/7/20 Mariano Martinez Peck <marianopeck@gmail.com>
I know we have just started with the Hudson server, but is there a way
to
see why a test is failing/error ? For the errors, at least we can see the PharoDebug.log ? THe other idea we have today (talking with Marcus) is to have RFB running in the hudson images. So that we can connect and browse it. Of course, it could be password protected so that not everybody can do it.
What do you think?
Cheers
Mariano
_______________________________________________ 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
-- Lukas Renggli www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (3)
-
Lukas Renggli -
Mariano Martinez Peck -
Nick Ager