[Pharo-project] 1.4 is now green...
.. 1.4 has now all tests green on jenkins (Mac and Linux). The nice side-effect is that all the jobs that check VM builds are now green, too. https://ci.lille.inria.fr/pharo/view/Pharo%201.4/ The idea is to now to just never ever integrate anything that makes a test break... Marcus -- Marcus Denker -- http://marcusdenker.de
On Sat, Mar 24, 2012 at 1:46 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
.. 1.4 has now all tests green on jenkins (Mac and Linux).
Yeahh. Thank you so much all of you and thank you Marcus. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
On Mar 24, 2012, at 1:46 PM, Marcus Denker wrote:
.. 1.4 has now all tests green on jenkins (Mac and Linux).
The nice side-effect is that all the jobs that check VM builds are now green, too.
https://ci.lille.inria.fr/pharo/view/Pharo%201.4/
The idea is to now to just never ever integrate anything that makes a test break...
ok but it means that we should run 20 min tests each we integrate somethingâ¦. how boring. We can try. Stef
Marcus
-- Marcus Denker -- http://marcusdenker.de
On Mar 24, 2012, at 3:28 PM, Stéphane Ducasse wrote:
On Mar 24, 2012, at 1:46 PM, Marcus Denker wrote:
.. 1.4 has now all tests green on jenkins (Mac and Linux).
The nice side-effect is that all the jobs that check VM builds are now green, too.
https://ci.lille.inria.fr/pharo/view/Pharo%201.4/
The idea is to now to just never ever integrate anything that makes a test break...
ok but it means that we should run 20 min tests each we integrate somethingâ¦. how boring. We can try.
Stef
That's why you should use a full automatized process .... :whistle: ^^ Ben
Marcus
-- Marcus Denker -- http://marcusdenker.de
.. 1.4 has now all tests green on jenkins (Mac and Linux).
The nice side-effect is that all the jobs that check VM builds are now green, too.
https://ci.lille.inria.fr/pharo/view/Pharo%201.4/
The idea is to now to just never ever integrate anything that makes a test break...
ok but it means that we should run 20 min tests each we integrate somethingâ¦. how boring. We can try.
Stef
That's why you should use a full automatized process .... :whistle: ^^
indeed. I want :) Stef
Stef, Naive question: could you simply let Jenkins do the testing, and investigate/roll-back if it reports problems? If Jenkins can reliably, based on unit tests, report a last successful build, you might be at a good place. In that world, you would integrate and let Jenkins tell you if it was a bad thing to do. Like I said, it might be naive. Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Stéphane Ducasse [stephane.ducasse@inria.fr] Sent: Saturday, March 24, 2012 10:37 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] 1.4 is now green...
.. 1.4 has now all tests green on jenkins (Mac and Linux).
The nice side-effect is that all the jobs that check VM builds are now green, too.
https://ci.lille.inria.fr/pharo/view/Pharo%201.4/
The idea is to now to just never ever integrate anything that makes a test break...
ok but it means that we should run 20 min tests each we integrate somethingâ¦. how boring. We can try.
Stef
That's why you should use a full automatized process .... :whistle: ^^
indeed. I want :) Stef
Then if I introduce a new test documenting an old bug, it will then be rejected right ? I wonder if I'd really want such a dumb system without an ounce of human expertise... Nicolas Le 24 mars 2012 15:37, Stéphane Ducasse <stephane.ducasse@inria.fr> a écrit :
.. 1.4 has now all tests green on jenkins (Mac and Linux).
The nice side-effect is that all the jobs that check VM builds are now
green, too.
https://ci.lille.inria.fr/pharo/view/Pharo%201.4/
The idea is to now to just never ever integrate anything that makes a
test break...
ok but it means that we should run 20 min tests each we integrate somethingâ¦. how boring. We can try.
Stef
That's why you should use a full automatized process .... :whistle: ^^
indeed. I want :)
Stef
On Mar 24, 2012, at 5:32 PM, Nicolas Cellier wrote:
Then if I introduce a new test documenting an old bug, it will then be rejected right ? I wonder if I'd really want such a dumb system without an ounce of human expertiseâ¦
This is not the idea :) How do I see the process: for the test we publish it in a bug entry and as soon as there a code that makes it green then we integrate it. Now we should have a way to say check that entry -> load the code -> run the tests and say if this is ok then in parallel - we should be able to look at the code - say ok please integrate - and the system does it So benjamin has a bunch of scripts for that. stef
Nicolas
Le 24 mars 2012 15:37, Stéphane Ducasse <stephane.ducasse@inria.fr> a écrit :
.. 1.4 has now all tests green on jenkins (Mac and Linux).
The nice side-effect is that all the jobs that check VM builds are now green, too.
https://ci.lille.inria.fr/pharo/view/Pharo%201.4/
The idea is to now to just never ever integrate anything that makes a test break...
ok but it means that we should run 20 min tests each we integrate somethingâ¦. how boring. We can try.
Stef
That's why you should use a full automatized process .... :whistle: ^^
indeed. I want :)
Stef
On Sat, Mar 24, 2012 at 1:46 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
.. 1.4 has now all tests green on jenkins (Mac and Linux).
The nice side-effect is that all the jobs that check VM builds are now green, too.
https://ci.lille.inria.fr/pharo/view/Pharo%201.4/
The idea is to now to just never ever integrate anything that makes a test break...
    Marcus
Great! The job "Project Pharo Kernel Reload Tests-Unix" is now green too, but it is quite unstable. And Kernel Tests need a lot of work. -- Pavel
-- Marcus Denker -- http://marcusdenker.de
participants (7)
-
Benjamin -
Damien Cassou -
Marcus Denker -
Nicolas Cellier -
Pavel Krivanek -
Schwab,Wilhelm K -
Stéphane Ducasse