September 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo CI Validation Timeout

by Guillermo Polito

I saw also that one of the linux slaves is much much slower than the others. Just check this: https://ci.inria.fr/pharo/job/30-Bootstrap/buildTimeTrend In one of the slaves the build takes one hour. In the other it takes 6. El miÃ©., 2 de sept. de 2015 a la(s) 9:11 a. m., Marcus Denker < marcus.denker(a)inria.fr> escribiÃ³: > I donât think soâ¦ the job used to run in 15 minutes. But we added more > tests, > Rules got slowerâ¦ > > On 02 Sep 2015, at 08:34, Nicolai Hess <nicolaihess(a)web.de> wrote: > > It is possible to see from the console output which rule or test takes a > lot time? > > 2015-09-02 8:09 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > >> >> On 01 Sep 2015, at 19:15, Ben Coman <btc(a)openinworld.com> wrote: >> >> Do you want to try a post-load... >> Delay delaySchedulerClass: DelayExperimentalSemaphoreScheduler >> >> which fixes the "super fast delay" on virtual machines reported here... >> http://comments.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/100873 >> >> Its named "experimental" only since it was integrated just before >> Pharo 4 release and did not have wide spread community testing, but >> its complete and working. There is some further overall streamlining >> of the DelayScheduler hierarchy I'd like to do later, but it would be >> good to give this one a run as the default for a while to see how it >> impacts the issue. (It would be good to get rough "CIAndRule: Timeout" >> before and after statistics.) >> >> btw, is that CI error indicating it times out after one hour? Are >> there any other timestamps present in the log that indicate if 1 hour >> really passed? >> >> >> Yes, I think soâ¦ >> >> https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/buildTimeTrend >> >> Now looking at it (no idea why it is chinese), it seems that we have some >> slowdown recently and all runs take 40-50 minutes, a slowdown to 60 can >> happen >> just by having less compute power available (or running multiple things >> in parallel). >> >> We should >> >> -> do a pass over slow tests >> -> do a pass over slow rules >> >> I will put the limit higher than 60 min for now. >> >> Marcus >> >> >> > >

Sept. 2, 2015

Re: [Pharo-dev] Removing name from Object

by Guillermo Polito

The problem is if (like in the past) name is extensively used by some library we depend upon (like... let's say morphic), a deprecation that raises an exception may turn the system unusable. It's not that it is not doable, but we should do it gently and with love. El miÃ©., 2 de sept. de 2015 a la(s) 9:30 a. m., Esteban Lorenzano < estebanlm(a)gmail.com> escribiÃ³: > On 02 Sep 2015, at 09:25, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > On Wed, Sep 2, 2015 at 8:40 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> How can we find out, which external projects depend on this? >> > > Is #name in any way special? Why not just deprecate it like any other > method change or removal? (And then remove it in Pharo 6) > > > +1 > thatâs the way to do it :) > > > Peter > > >

Sept. 2, 2015

Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp

by stepharo

for your info... Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp Stef

Sept. 2, 2015

size of MCbrowser should be proportional

by stepharo

Hi guys now when I open MCBrowser it gets 80% of my window. So this is good to make it larger but it should be proportional to the actual size. https://pharo.fogbugz.com/f/cases/16451/MCBrowser-default-size-should-propo… Could the person that originally changed it fix it? Stef

Sept. 2, 2015

Re: [Pharo-dev] Removing name from Object

by Esteban Lorenzano

> On 02 Sep 2015, at 09:25, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > On Wed, Sep 2, 2015 at 8:40 AM, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: > How can we find out, which external projects depend on this? > > Is #name in any way special? Why not just deprecate it like any other method change or removal? (And then remove it in Pharo 6) +1 thatâs the way to do it :) > > Peter

Sept. 2, 2015

Re: [Pharo-dev] Removing name from Object

by Peter UhnÃ¡k

On Wed, Sep 2, 2015 at 8:40 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > How can we find out, which external projects depend on this? > Is #name in any way special? Why not just deprecate it like any other method change or removal? (And then remove it in Pharo 6) Peter

Sept. 2, 2015

Re: [Pharo-dev] Removing name from Object

by stepharo

Good idea I will try when I have a moment to relax. I'm in a little focused hacking sprint then admin sprint :) Le 1/9/15 22:02, Sven Van Caekenberghe a Ã©crit : >> On 01 Sep 2015, at 21:44, stepharo <stepharo(a)free.fr> wrote: >> >> Hi guys >> >> I would love to see name removed from Object. It brings more problems than anything else. >> Any taker? >> >> Stef > I tried it in the past. I just tried again on the latest #50297. > > I did put a 'self haltOnce' in Object>>#name and with 'Halt enableHaltOnce' I can still browse and run all Zinc-Tests so we might be closer than we thought. > > In any case, almost any code that needs Object>>#name could probably we rewritten to send #printString (being lazy). > > Sven > > >

Sept. 2, 2015

Re: [Pharo-dev] Pharo CI Validation Timeout

by Marcus Denker

I donât think soâ¦ the job used to run in 15 minutes. But we added more tests, Rules got slowerâ¦ > On 02 Sep 2015, at 08:34, Nicolai Hess <nicolaihess(a)web.de> wrote: > > It is possible to see from the console output which rule or test takes a lot time? > > 2015-09-02 8:09 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>>: > >> On 01 Sep 2015, at 19:15, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: >> >> Do you want to try a post-load... >> Delay delaySchedulerClass: DelayExperimentalSemaphoreScheduler >> >> which fixes the "super fast delay" on virtual machines reported here... >> http://comments.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/100873 <http://comments.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/100873> >> >> Its named "experimental" only since it was integrated just before >> Pharo 4 release and did not have wide spread community testing, but >> its complete and working. There is some further overall streamlining >> of the DelayScheduler hierarchy I'd like to do later, but it would be >> good to give this one a run as the default for a while to see how it >> impacts the issue. (It would be good to get rough "CIAndRule: Timeout" >> before and after statistics.) >> >> btw, is that CI error indicating it times out after one hour? Are >> there any other timestamps present in the log that indicate if 1 hour >> really passed? >> > > Yes, I think soâ¦ > > https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/buildTimeTrend <https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/buildTimeTrend> > > Now looking at it (no idea why it is chinese), it seems that we have some > slowdown recently and all runs take 40-50 minutes, a slowdown to 60 can happen > just by having less compute power available (or running multiple things in parallel). > > We should > > -> do a pass over slow tests > -> do a pass over slow rules > > I will put the limit higher than 60 min for now. > > Marcus > > >

Sept. 2, 2015

Re: [Pharo-dev] Removing name from Object

by Nicolai Hess

How can we find out, which external projects depend on this? 2015-09-02 7:06 GMT+02:00 H. Hirzel <hannes.hirzel(a)gmail.com>: > On 9/1/15, stepharo <stepharo(a)free.fr> wrote: > > Hi guys > > > > I would love to see name removed from Object. It brings more problems > > than anything else. > > Any taker? > > > > Stef > > > > > > > > Hi Stef > > About > > Object>> > name > "Answer a name for the receiver. This is used generically in the > title of certain inspectors, such as the referred-to inspector, and > specificially by various subsystems. By default, we let the object > just print itself out.. " > > ^ self printString > > > Are you refering to this > > http://comments.gmane.org/gmane.comp.lang.smalltalk.pharo.user/21476? > > Which other kinds of problems do you see with this method? > > Could you elaborate a bit please why you want to remove Object>>name? > > Regards > > Hannes > >

Sept. 2, 2015

Re: [Pharo-dev] Pharo CI Validation Timeout

by Nicolai Hess

It is possible to see from the console output which rule or test takes a lot time? 2015-09-02 8:09 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > > On 01 Sep 2015, at 19:15, Ben Coman <btc(a)openinworld.com> wrote: > > Do you want to try a post-load... > Delay delaySchedulerClass: DelayExperimentalSemaphoreScheduler > > which fixes the "super fast delay" on virtual machines reported here... > http://comments.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/100873 > > Its named "experimental" only since it was integrated just before > Pharo 4 release and did not have wide spread community testing, but > its complete and working. There is some further overall streamlining > of the DelayScheduler hierarchy I'd like to do later, but it would be > good to give this one a run as the default for a while to see how it > impacts the issue. (It would be good to get rough "CIAndRule: Timeout" > before and after statistics.) > > btw, is that CI error indicating it times out after one hour? Are > there any other timestamps present in the log that indicate if 1 hour > really passed? > > > Yes, I think soâ¦ > > https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/buildTimeTrend > > Now looking at it (no idea why it is chinese), it seems that we have some > slowdown recently and all runs take 40-50 minutes, a slowdown to 60 can > happen > just by having less compute power available (or running multiple things in > parallel). > > We should > > -> do a pass over slow tests > -> do a pass over slow rules > > I will put the limit higher than 60 min for now. > > Marcus > > >

Sept. 2, 2015