- Pharo-dev - lists.pharo.org

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

Re: [Pharo-dev] Is Pharo spying on me?
by Tudor Girba Dec. 6, 2017

Dec. 6, 2017

Hi, An interesting point. However, just because other people behave less nicely does not mean we should be the same. Principles should always remain principles regardless of how inconvenient or apparently insignificant the situation is. Cheers, Doru > On Dec 6, 2017, at 12:00 PM, Benoit St-Jean via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Benoit St-Jean <bstjean(a)yahoo.com> > Subject: Re: [Pharo-dev] Is Pharo spying on me? > Date: December 6, 2017 at 12:00:31 PM GMT+1 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Reply-To: Benoit St-Jean <bstjean(a)yahoo.com> > > > Let's not panic here! > > Funny to see people worry so much about privacy from a tool that collects technical data anonymously when a gazillion agencies (especially NSA) keep track of every email and phone call we do!!! > > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > > > From: Tudor Girba <tudor(a)tudorgirba.com> > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Sent: Wednesday, December 6, 2017 1:13 AM > Subject: Re: [Pharo-dev] Is Pharo spying on me? > > Hi, > > What exactly are we removing? > > Cheers, > Doru > > > > On Dec 5, 2017, at 9:41 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > but you are asked to share it, this is not collected automatically without asking before. > > > > anyway, we are removing that (if not removed yet) > > > >> On 5 Dec 2017, at 21:34, Sean Glazier <sglazier456(a)gmail.com> wrote: > >> > >> Personally, I know of work places where this is not going to be allowed. I understand they need the data, but you need to be able to turn it off. A secure facility would not allow the transmission out in any case. > >> > >> > >> Kind Regards, > >> > >> Sean Glazier > >> > >> > >> On Tue, Dec 5, 2017 at 2:45 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > >> Check Privacy section in Settings Browser. > >> If you ever send anything, data are anonymized. > >> Developers use it to be able to evaluate their research (PhD) work. It is a requirement in the research field. > >> By sending the anonymized data, you help developers to understand how their tools are used. > >> In particular, I am aware of Spotter, Quality Assistant, GT tools, and Roassal. > >> > >> Cheers, > >> Juraj > >> > >> > On Dec 5, 2017, at 16:30, Bernhard Pieber <bernhard(a)pieber.com> wrote: > >> > > >> > I just found a file named org.pharo.global-identifiers.ston in my preferences folder. It contains a #secretUUID and a #computerUUID. :-( What is this information used for? More importantly, how can I turn it off? > >> > > >> > Bernhard > >> > >> > >> > > > > -- > www.tudorgirba.com > www.feenk.com > > "Next time you see your life passing by, say 'hi' and get to know her." > > > > > > > > Virus-free. www.avg.com > > -- www.tudorgirba.com www.feenk.com "What we can governs what we wish."

1 0

Re: [Pharo-dev] How to get a Moose Model
by Tudor Girba Dec. 6, 2017

Dec. 6, 2017

Hi, Thanks for the question. Please address this to the moose-dev mailing list (in CC): https://www.list.inf.unibe.ch/listinfo/moose-dev I just answered it there. Cheers, Doru > On Dec 5, 2017, at 4:44 PM, Moussa Saker via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Moussa Saker <sak_moussa(a)yahoo.fr> > Subject: How to get a Moose Model > Date: December 5, 2017 at 4:44:31 PM GMT+1 > To: "pharo-dev(a)lists.pharo.org" <pharo-dev(a)lists.pharo.org> > Reply-To: Moussa Saker <sak_moussa(a)yahoo.fr> > > > Hello everyone > > we are working on a Moose project and we need a script to import the Moose Model, right now we use: > > MooseModel root first , > > but it's not really practical, Any suggestions ? > > Moussa Saker > LISCO Laboratory > Badji Mokhtar-Annaba University, > P.O. Box 12, Annaba 23000, Algeriai n > > -- www.tudorgirba.com www.feenk.com "To lead is not to demand things, it is to make them happen."

1 0