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

Re: [Pharo-dev] The 6.1 Space Monkey is unhappy

by Marcus Denker

>> >> What needs to be done? >> >> -> your change can be accepted as we know it does not fail more fixes >> -> then we need fix the tests in Pharo6 >> -> in a perfect world we would update the slice checker to only fail for >> now test failingâ¦ (it used to be lille thatâ¦). > > I must say that It made the validation two times slower, fragile and > led to the hiding of problems instead of solving themâ¦ > Yes, true. Marcus

March 5, 2018

Re: [Pharo-dev] The 6.1 Space Monkey is unhappy

by Pavel Krivanek

2018-03-05 10:54 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > > >> On 5 Mar 2018, at 10:27, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> Hi Marcus, >> >> On 5 March 2018 at 09:23, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> >>>> On 5 Mar 2018, at 09:16, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>>> >>>> Hi Esteban & Marcus, >>>> >>>> I'm getting repeated validation failures for: >>>> >>>> https://pharo.manuscript.com/f/cases/21431 >>>> >>>> >>>> It's the same set of tests that fail each time, and as far as I can >>>> tell they have nothing to do with the patch I submitted. >>>> >>>> Do you know if this is happening on other tests? >>> >>> I saw that Saturday but decided to wait till Monday (weekends are important..). >>> >>> So: no, I have *no* idea what happened. From one CI run to the next, >>> suddenly around 160 tests related to Calypso started failing due to a missing method. >>> >>> Now starting from sometime today, this problem stoped. The last failing PR checks >>> fail due to different reasonsâ¦ >>> >>> And I have no idea why. >>> >>> (And yes, we al know that >>> 1) the PR checks need more compute power, too slow >>> 2) we *need* to track down the reason why still *a lot* of times the PR fails >>> even though it should not. >>> >>> The problem is that just keeping a build alive of this kind is a full time job.. that >>> we have nobody doing, so many many people do as much as they can and we >>> hope it will get betterâ¦.) >> >> Thanks for the update. >> > > Oh, and it was completely unrelated. Your change is for Pharo6... > >> I took a look at the failures and it appears that >> >> BehaviorTest>>testBehaviorRespectsPolymorphismWithTraitBehavior >> ClassDescriptionTest>>testClassDescriptionRespectsPolymorphismWithTraitDescription >> ClassTest>>testClassRespectsPolymorphismWithTrait >> >> are all failing due to changes in Fuel - methods were changed from >> traits to local methods. >> > Yes, the problem is that the monkey (the contribution checker) fails as soon > as there are errors even in the main image. > > The last Pharo6 has these tests failing, so now all contribution checks for > Pharo6 fail. > > What needs to be done? > > -> your change can be accepted as we know it does not fail more fixes > -> then we need fix the tests in Pharo6 > -> in a perfect world we would update the slice checker to only fail for > now test failingâ¦ (it used to be lille thatâ¦). I must say that It made the validation two times slower, fragile and led to the hiding of problems instead of solving them... -- Pavel > > As I said: this is a full time jobâ¦ > > Marcus

March 5, 2018

[Pharo 7.0-dev] Build #647: 21488 Remove unnecessary debug output/debig code from #testPrintNameOn

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #647 was: SUCCESS. The Pull Request #1021 was integrated: "21488 Remove unnecessary debug output/debig code from #testPrintNameOn" Pull request url: https://github.com/pharo-project/pharo/pull/1021 Issue Url: https://pharo.fogbugz.com/f/cases/21488 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 5, 2018

Re: [Pharo-dev] The 6.1 Space Monkey is unhappy

by Marcus Denker

> On 5 Mar 2018, at 10:27, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Marcus, > > On 5 March 2018 at 09:23, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >>> On 5 Mar 2018, at 09:16, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>> >>> Hi Esteban & Marcus, >>> >>> I'm getting repeated validation failures for: >>> >>> https://pharo.manuscript.com/f/cases/21431 >>> >>> >>> It's the same set of tests that fail each time, and as far as I can >>> tell they have nothing to do with the patch I submitted. >>> >>> Do you know if this is happening on other tests? >> >> I saw that Saturday but decided to wait till Monday (weekends are important..). >> >> So: no, I have *no* idea what happened. From one CI run to the next, >> suddenly around 160 tests related to Calypso started failing due to a missing method. >> >> Now starting from sometime today, this problem stoped. The last failing PR checks >> fail due to different reasonsâ¦ >> >> And I have no idea why. >> >> (And yes, we al know that >> 1) the PR checks need more compute power, too slow >> 2) we *need* to track down the reason why still *a lot* of times the PR fails >> even though it should not. >> >> The problem is that just keeping a build alive of this kind is a full time job.. that >> we have nobody doing, so many many people do as much as they can and we >> hope it will get betterâ¦.) > > Thanks for the update. > Oh, and it was completely unrelated. Your change is for Pharo6... > I took a look at the failures and it appears that > > BehaviorTest>>testBehaviorRespectsPolymorphismWithTraitBehavior > ClassDescriptionTest>>testClassDescriptionRespectsPolymorphismWithTraitDescription > ClassTest>>testClassRespectsPolymorphismWithTrait > > are all failing due to changes in Fuel - methods were changed from > traits to local methods. > Yes, the problem is that the monkey (the contribution checker) fails as soon as there are errors even in the main image. The last Pharo6 has these tests failing, so now all contribution checks for Pharo6 fail. What needs to be done? -> your change can be accepted as we know it does not fail more fixes -> then we need fix the tests in Pharo6 -> in a perfect world we would update the slice checker to only fail for now test failingâ¦ (it used to be lille thatâ¦). As I said: this is a full time jobâ¦ Marcus

March 5, 2018

Pavel's ChangeLog week of 2018-02-26

by Pavel Krivanek

Hi, Guille is working on the Iceberg improvements and he wanted to be able to open a terminal window on top of the repository and interact with it via the command line. So we looked at this issue because I already in December made some experiments with the terminal emulation in Pharo. In past, the Squeak had a working terminal emulation that used PseudoTTYPlugin. The VM is not built with this code for a long time but I tried to replace it with a small C library and then wrote an FFI interface to it. Together with that, I ported most of the old code Squeak code to Pharo. With Guille we tried to avoid usage of such external library and wrote an FFI interface to all the required LibC functions. We were successful but we realized that there are several issues that are limiting us. When you want to execute a separate process for the program that you want to open in terminal (typically the Bash), you need to redirect the standard IO files, create a fork of your process, do some additional initialization in it and call 'exec' on it. In the parent process, you change redirected IO files back to the original values. But the problem is that between the FFI calls from Smalltalk the VM can do a lot of things including garbage collection etc. On OS X the fork() function has the following limitation described in man: "There are limits to what you can do in the child process. To be totally safe you should restrict your yourself to only executing async-signal safe operations until such time as one of the exec functions is called. All APIs, including global data symbols, in any framework or library should be assumed to be unsafe after a fork() unless explicitly documented to be safe or async-signal safe. If you need to use these frameworks in the child process, you must exec. In this situation it is reasonable to exec your-self. yourself." As the result in most cases (but not all) the fork() and exec() pair from the Smalltalk side fails on OS X. Linux does not have this limitation however even there we found an issue. It is bound to the fact that fork() makes a fork of all the parent process that uses the same resources. As soon as Pharo is opened in a window and X11 is involved (the window wants to be repainted), it can lead to the VM crash. So we learned that unfortunately we currently cannot use image-only FFI code for this task. We need a C library or VM plugin. The repository of the terminal emulator is here: https://github.com/pavel-krivanek/terminal and can be loaded using the following code: Metacello new baseline: 'TerminalEmulator'; repository: 'github://pavel-krivanek/terminal/src'; load. #TerminalEmulator asClass compileLibrary. â It compiles and links the small library with only one function using the GCC so the machine needs to have a proper development environment. The terminal emulator is in very early stage and has a lot of issues like processes cleanup, drawing, keyboard input etc. etc. If you are interested in it, feel free to contribute. Cheers, -- Pavel

March 5, 2018

Re: [Pharo-dev] The 6.1 Space Monkey is unhappy

by Alistair Grant

Hi Marcus, On 5 March 2018 at 09:23, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 5 Mar 2018, at 09:16, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> Hi Esteban & Marcus, >> >> I'm getting repeated validation failures for: >> >> https://pharo.manuscript.com/f/cases/21431 >> >> >> It's the same set of tests that fail each time, and as far as I can >> tell they have nothing to do with the patch I submitted. >> >> Do you know if this is happening on other tests? > > I saw that Saturday but decided to wait till Monday (weekends are important..). > > So: no, I have *no* idea what happened. From one CI run to the next, > suddenly around 160 tests related to Calypso started failing due to a missing method. > > Now starting from sometime today, this problem stoped. The last failing PR checks > fail due to different reasonsâ¦ > > And I have no idea why. > > (And yes, we al know that > 1) the PR checks need more compute power, too slow > 2) we *need* to track down the reason why still *a lot* of times the PR fails > even though it should not. > > The problem is that just keeping a build alive of this kind is a full time job.. that > we have nobody doing, so many many people do as much as they can and we > hope it will get betterâ¦.) Thanks for the update. I took a look at the failures and it appears that BehaviorTest>>testBehaviorRespectsPolymorphismWithTraitBehavior ClassDescriptionTest>>testClassDescriptionRespectsPolymorphismWithTraitDescription ClassTest>>testClassRespectsPolymorphismWithTrait are all failing due to changes in Fuel - methods were changed from traits to local methods. I'll try and track down when the change was introduced and by whom, but hopefully it is just a matter of updating the tests. Cheers, Alistair

March 5, 2018

Re: [Pharo-dev] The 6.1 Space Monkey is unhappy

by Marcus Denker

> On 5 Mar 2018, at 09:16, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Esteban & Marcus, > > I'm getting repeated validation failures for: > > https://pharo.manuscript.com/f/cases/21431 > > > It's the same set of tests that fail each time, and as far as I can > tell they have nothing to do with the patch I submitted. > > Do you know if this is happening on other tests? I saw that Saturday but decided to wait till Monday (weekends are important..). So: no, I have *no* idea what happened. From one CI run to the next, suddenly around 160 tests related to Calypso started failing due to a missing method. Now starting from sometime today, this problem stoped. The last failing PR checks fail due to different reasonsâ¦ And I have no idea why. (And yes, we al know that 1) the PR checks need more compute power, too slow 2) we *need* to track down the reason why still *a lot* of times the PR fails even though it should not. The problem is that just keeping a build alive of this kind is a full time job.. that we have nobody doing, so many many people do as much as they can and we hope it will get betterâ¦.) Marcus

March 5, 2018

The 6.1 Space Monkey is unhappy

by Alistair Grant

Hi Esteban & Marcus, I'm getting repeated validation failures for: https://pharo.manuscript.com/f/cases/21431 It's the same set of tests that fail each time, and as far as I can tell they have nothing to do with the patch I submitted. Do you know if this is happening on other tests? Thanks very much, Alistair

March 5, 2018

Esteban's ChangeLog week of 26 February 2018

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 26 February 2018 to 4 March 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=26/2/2018&to=4/3/2018 ChangeLog ========= 2 March 2018: ------------- * I've been working on Iceberg UI. I have first versions of: * repositories browser * individual repository browser * individual repository management browser * commit window * push window * pull windows I'm not woking on fix a couple of problems on refreshing windows and defining how the pull will work (by default, it will trigger a merge of the changes your are pulling into your image). 1 March 2018: ------------- * I made a new backport for 6.1, [case: 21344](https://pharo.fogbugz.com/f/cases/21344) enjoy 28 February 2018: ----------------- * Well... I spent an stupid amount of time to figure out why the latest VM for macOS was not including libgit2. Turns out, there was a "deploy filter" problem (two problems, in fact), that was making that all pharo flavours were being uploaded to the file server and with same name so in fact, one flavour was being copied on top of the other. And "lowcode VM", for example, does not includes libgi2. So, now that's fixed. You can start using latest VM again (which is the one that is signed) ;) cheers! Esteban

March 5, 2018

Re: [Pharo-dev] [Pharo-users] Looking for names for the booklet collection

by Peter UhnÃ¡k

> Pharo Tools & Technologies > Pharo Language & Environment +1 ... simple, obvious, to the point please no cryptic/"clever" names On Sun, Mar 4, 2018 at 4:41 PM, Benoit St-Jean via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: Benoit St-Jean <bstjean(a)yahoo.com> > To: Pharo Development List <pharo-dev(a)lists.pharo.org>, Ben Coman < > btc(a)openinworld.com> > Cc: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Bcc: > Date: Sun, 4 Mar 2018 15:41:10 +0000 (UTC) > Subject: Re: [Pharo-dev] Looking for names for the booklet collection > Why not simply: > > Pharo Tools & Technologies > Pharo Language & Environment > > ----------------- > 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) > > > On Sunday, March 4, 2018, 10:30:46 AM EST, Ben Coman <btc(a)openinworld.com> > wrote: > > > > > On 4 March 2018 at 20:21, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > Hi > > I would like to make a distinction between booklet on Pharo > technologies (Smacc, Voyage, Scraping ...) and the booklets more > oriented towards teaching something with pharo (building an > interpreter, a reflective language...) > > > Pharo Applications / Inside Pharo > > Over Pharo / Under Pharo > > > Right now we have The Pharo Booklet Collection. > And I'm looking for two names > > the Pharo academic booklet collection ? > and > the Pharo technology booklet collection ? > > > Pharology / Pharocraft > > > cheers -ben > > > > > > > >

March 4, 2018