March 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] Pharo 1.4 Tests-Unix - Build # 307 - Unstable!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr March 25, 2012

March 25, 2012

1 0

[Pharo-project] [update 1.4] #14412
by Marcus Denker March 25, 2012

March 25, 2012

14412 ----- Issue 5538: Package MethodConverters should be merged with Tools http://code.google.com/p/pharo/issues/detail?id=5538 Issue 5540: Remove wrong dirty package System http://code.google.com/p/pharo/issues/detail?id=5540 Issue 5543: SmalltalkImage: move all deprecated method to Deprecated14 http://code.google.com/p/pharo/issues/detail?id=5543 Issue 5541: Clean GrafPort more... http://code.google.com/p/pharo/issues/detail?id=5541 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] 1.4 is now green...
by Marcus Denker March 24, 2012

March 24, 2012

.. 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

7 8

[Pharo-project] simplified main page http://www.pharo-project.org
by Marcus Denker March 24, 2012

March 24, 2012

Hi, Instead of the cryptic "shortcuts" section, the main page now has a download section: http://www.pharo-project.org -- Marcus Denker -- http://marcusdenker.de

2 1

[Pharo-project] speeding up BigNum/Fractions calculations using NativeBoost?
by Lawson English March 24, 2012

March 24, 2012

I'd like to see how fast a Mandelbrot Set algorithm could be implemented in Squeak/Pharo by using NativeBoost to bypass the VM whenever possible. Is that a worthwhile optimization, do you think? Lawson

1 0

[Pharo-project] Updated DL Links http://www.pharo-project.org/pharo-download/release-1-3
by Marcus Denker March 24, 2012

March 24, 2012

Hi, http://www.pharo-project.org/pharo-download/release-1-3 -> "Pharo 1.3" and "PharoCore 1.3" download links now point to 13327 zips on Gforge -> VM downloads point to latest successful build on Jenkins for Win,Linux and Mac. TODO: -> update one-Click. Christophe has a test job for a 1.4 one-click that takes the last successfull build of all VMs: https://ci.lille.inria.fr/pharo/job/Pharo%20One%20Click%20image/ This will be added to the jobs of Pharo 1.3 and Pharo 1.4 (and Aida) soon. -> 1.3 has some faling tests and tracker entries that should be fixed http://code.google.com/p/pharo/issues/list?can=2&q=milestone%3D1.3 Marcus -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Pharo Kernel Reload Tests-Unix - Build # 37 - Still unstable!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr March 24, 2012

March 24, 2012

1 0

[Pharo-project] Transcript lost
by Pavel Krivanek March 24, 2012

March 24, 2012

Hi, it seems that we lost the Transcript item from the Tools menu :-) -- Pavel

3 2

[Pharo-project] [update 1.4] #14411
by Marcus Denker March 24, 2012

March 24, 2012

14411 ----- Issue 5537: Transcript needs entry in Tools menu http://code.google.com/p/pharo/issues/detail?id=5537 Issue 5533: Move startup script and emergency evaluator from Tools to System menu http://code.google.com/p/pharo/issues/detail?id=5533 Issue 3573: New test: CompiledMethodTest.testPerformInSuperclassCanExecutelongMethodWithTemps http://code.google.com/p/pharo/issues/detail?id=3573 Issue 5474: EventHandler Test + Better use of handler http://code.google.com/p/pharo/issues/detail?id=5474 -- Marcus Denker -- http://marcusdenker.de

1 0

Re: [Pharo-project] 1.4 is now green...
by Marcus Denker March 24, 2012

March 24, 2012

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 ? No, it will be added to the bug tracker. > I wonder if I'd really want such a dumb system without an ounce of human expertise... > In the past we did exactly that: add failing tests, so we will forced to fix them! The thing is: it did not work. Nobody cares about fixing failing tests. The only result is that the build is in the state "some tests are failing". A week later "some more tests are failing". A month later "When did that test start to fail ?!". In addition: how do we know that a vm build is good? That we are in a good state? Marcus -- Marcus Denker -- http://marcusdenker.de

1 0