- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #365: 20830 Super setup need to be called in Monticello tests and other cleanups (comments, tags)
by ci-pharo-ci-jenkins2＠inria.fr Dec. 7, 2017

Dec. 7, 2017

There is a new Pharo build available! The status of the build #365 was: SUCCESS. The Pull Request #583 was integrated: "20830 Super setup need to be called in Monticello tests and other cleanups (comments, tags)" Pull request url: https://github.com/pharo-project/pharo/pull/583 Issue Url: https://pharo.fogbugz.com/f/cases/20830 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #364: 20816 Typo in DateAndTimeEpochTest and DateAndTimeUnixEpochTest tearDown
by ci-pharo-ci-jenkins2＠inria.fr Dec. 7, 2017

Dec. 7, 2017

There is a new Pharo build available! The status of the build #364 was: FAILURE. The Pull Request #572 was integrated: "20816 Typo in DateAndTimeEpochTest and DateAndTimeUnixEpochTest tearDown" Pull request url: https://github.com/pharo-project/pharo/pull/572 Issue Url: https://pharo.fogbugz.com/f/cases/20816 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Running tests in MCMethodDefinitionTest
by Torsten Bergmann Dec. 7, 2017

Dec. 7, 2017

Hi, a little story: while working on cleaning up MCMethodDefinitionTest (see https://pharo.fogbugz.com/f/cases/20830) I noticed that from time to time you have trouble when running the test methods in this class one after the other several times. So sometimes it worked and sometimes not. I wondered since the latest Pharo 7 build #70360 is definitely green on CI, so the tests seem to work. After investigating I've noticed that in MCMethodDefinitionTest>>tearDown a package "FooBarBaz" which is used during the tests is unregistered and (when you run another test from this suite right afterwards) is not found anymore. Because in the test initialization it is not. This is easily fixed with setting the package up in the #setUp method which is unregistered in #tearDown and one can easily run the tests several times independently. So if one had trouble in Pharo 6 and Pharo 7 with sporadic fails in Monticello tests this might have been the cause. The fix is part of PR https://github.com/pharo-project/pharo/pull/583 Bye T.

3 2

[Pharo 7.0-dev] Build #363: 20825 Super setUp need to be called in Opal Compiler tests
by ci-pharo-ci-jenkins2＠inria.fr Dec. 7, 2017

Dec. 7, 2017

There is a new Pharo build available! The status of the build #363 was: SUCCESS. The Pull Request #578 was integrated: "20825 Super setUp need to be called in Opal Compiler tests" Pull request url: https://github.com/pharo-project/pharo/pull/578 Issue Url: https://pharo.fogbugz.com/f/cases/20825 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #362: 20819 Fix variable assignment in RBScanner>>stripComment
by ci-pharo-ci-jenkins2＠inria.fr Dec. 7, 2017

Dec. 7, 2017

There is a new Pharo build available! The status of the build #362 was: SUCCESS. The Pull Request #573 was integrated: "20819 Fix variable assignment in RBScanner>>stripComment" Pull request url: https://github.com/pharo-project/pharo/pull/573 Issue Url: https://pharo.fogbugz.com/f/cases/20819 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Next OpenSmalltalkVM Release Planned For February 1
by Torsten Bergmann Dec. 7, 2017

Dec. 7, 2017

see http://forum.world.st/ANN-Next-OpenSmalltalkVM-Release-Planned-For-February… What does it mean for Pharo-VM and release planning? Thx T.

1 0

[Pharo 7.0-dev] Build #361: 20827 Super setUp need to be called RBParseTreeRewriterTest and RBParseTreeSearcherTest
by ci-pharo-ci-jenkins2＠inria.fr Dec. 7, 2017

Dec. 7, 2017

There is a new Pharo build available! The status of the build #361 was: SUCCESS. The Pull Request #580 was integrated: "20827 Super setUp need to be called RBParseTreeRewriterTest and RBParseTreeSearcherTest" Pull request url: https://github.com/pharo-project/pharo/pull/580 Issue Url: https://pharo.fogbugz.com/f/cases/20827 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Corrupt method source in Pharo 6.1 (stable)
by Bernhard Pieber Dec. 6, 2017

Dec. 6, 2017

I did the following in Pharo Launcher: 1. Select Official distributions > Pharo 6.1 (stable) 2. Click Create Image 3. Launch created image 4. Browse GLMAccumulator 5. Click on any method, e.g. activeEntity => method source is corrupt, e.g. mp: âtg 2/2/2010 22:03' I tried it twice, also with the Pharo 6.0 > latest image. Can anyone else confirm that? Bernhard

3 4

[Pharo 7.0-dev] Build #360: 20814 Add release check that we have no protocols left without methods
by ci-pharo-ci-jenkins2＠inria.fr Dec. 6, 2017

Dec. 6, 2017

There is a new Pharo build available! The status of the build #360 was: SUCCESS. The Pull Request #570 was integrated: "20814 Add release check that we have no protocols left without methods" Pull request url: https://github.com/pharo-project/pharo/pull/570 Issue Url: https://pharo.fogbugz.com/f/cases/20814 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #359: 20815 Add a release test ensuring that there are no empty packages in the i
by ci-pharo-ci-jenkins2＠inria.fr Dec. 6, 2017

Dec. 6, 2017

There is a new Pharo build available! The status of the build #359 was: SUCCESS. The Pull Request #571 was integrated: "20815 Add a release test ensuring that there are no empty packages in the i" Pull request url: https://github.com/pharo-project/pharo/pull/571 Issue Url: https://pharo.fogbugz.com/f/cases/20815 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0