- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #1319: 22556-Reverting-slots-to-return-the-set-of-installed-slots-in-the-class-
by ci-pharo-ci-jenkins2＠inria.fr Oct. 9, 2018

Oct. 9, 2018

There is a new Pharo build available! The status of the build #1319 was: FAILURE. The Pull Request #1892 was integrated: "22556-Reverting-slots-to-return-the-set-of-installed-slots-in-the-class-" Pull request url: https://github.com/pharo-project/pharo/pull/1892 Issue Url: https://pharo.fogbugz.com/f/cases/22556 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1318: 22492-Self-Hosted Gitlab support
by ci-pharo-ci-jenkins2＠inria.fr Oct. 8, 2018

Oct. 8, 2018

There is a new Pharo build available! The status of the build #1318 was: SUCCESS. The Pull Request #1828 was integrated: "22492-Self-Hosted Gitlab support" Pull request url: https://github.com/pharo-project/pharo/pull/1828 Issue Url: https://pharo.fogbugz.com/f/cases/self_hosted_gitlab Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1317: 22545-The-64-bit-image-does-not-have-the-correct-display-size-again
by ci-pharo-ci-jenkins2＠inria.fr Oct. 8, 2018

Oct. 8, 2018

There is a new Pharo build available! The status of the build #1317 was: SUCCESS. The Pull Request #1884 was integrated: "22545-The-64-bit-image-does-not-have-the-correct-display-size-again" Pull request url: https://github.com/pharo-project/pharo/pull/1884 Issue Url: https://pharo.fogbugz.com/f/cases/22545 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1316: 22541 Tag and comment ManifestGTSpotter
by ci-pharo-ci-jenkins2＠inria.fr Oct. 8, 2018

Oct. 8, 2018

There is a new Pharo build available! The status of the build #1316 was: SUCCESS. The Pull Request #1879 was integrated: "22541 Tag and comment ManifestGTSpotter" Pull request url: https://github.com/pharo-project/pharo/pull/1879 Issue Url: https://pharo.fogbugz.com/f/cases/22541 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Esteban's ChangeLog week of 1 October 2018
by estebanlm＠gmail.com Oct. 8, 2018

Oct. 8, 2018

Hello! This is my weekly ChangeLog, from 1 October 2018 to 7 October 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=1/10/2018&to=7/10/2018 ChangeLog ========= 5 October 2018: --------------- * I made a couple of backports to Pharo 6.1 * [case: 22517](https://pharo.fogbugz.com/f/cases/22517) : Update ProfStef and fix spelling mistakes * [case: 22535](https://pharo.fogbugz.com/f/cases/22535) : Backport Tonel v1.0.9 to Pharo 6.1 * I finished a "simple" [PR for Calypso](https://github.com/pharo-ide/Calypso/pull/330): It was about better exposing the usage of certain command when using the +cmd+/+ Calypso-Spotter help. Now, this was not obvious because this correspons to a command nobody is using it yet, but it will become important as we enhance discoverability of it :) 2 October 2018: --------------- * Well... I spent the full day debugging on smalltalkCI to send a [new fix](https://github.com/hpi-swa/smalltalkCI/pull/399) to allow the load of projects with packages already installed in the image. This is very useful for us, developing Pharo and their components. * Spec * Calypso * Iceberg * Zinc * etc. And maybe it will be useful for others in the future. cheers! Esteban

1 0

Re: [Pharo-dev] [squeak-dev] DelayIdleScheduler experiment
by Ben Coman Oct. 7, 2018

Oct. 7, 2018

Hi Tim, Thanks for your feedback On Mon, 8 Oct 2018 at 01:27, tim Rowledge <tim(a)rowledge.org> wrote: > I may be out of date on this but I think that the Cog setup makes it > possible to have a timer check every 2mS by default. The > relinquishProcessor stuff was a definite hack to try to reduce cpu usage on > laptoppy things and I don't think anyone ever expected it to be used for > more than 1mS sleeps. It was one of those "I wonder if this will improve > anything?" ideas that got left in place. > > Surely the ideal would be to > a) as you point out, add this delay to the main delay list > Its not a separate delay. The "activeDelay" is split into separate pieces relinquished around asynchronous I/O like mouse, etc. b) find a way to provide an outside timer to trigger the delay at the top > of the list rather than relying on the vm eventually checking the tick etc. > The key thing is to inform the VM that there are no runnable processes and pause the main-native-thread and heartbeat-thread until the next image-scheduled wakeup time. One alternative may be to adapt #primSignal:atUTCMicroseconds: to be #primSignal:atUTCMicroseconds:idle: > > Interestingly, we have the threaded ticker for many systems as part of the > Cog vm. I don't know if it works on all systems; I do know it would be > 'interesting' to implement on RISC OS, but that's life. A quick look at > unix/sqUnixHeartbeat.c suggests to me that it might be plausible to use > variable length beats Q: does the main-native-thread stop running if the heatbeat stops? > and tie the time to any sooner-than-2mS event wanted. We'd (probably) change Delay handling to behave as if there were always a 1 > or 2mS (fake)delay even if the nearest actual Delay were far beyond that. > I can't follow where you are going with that. If your on a cloud server, you may want to idle for minutes or hours without processing delays, and restarting delays when I/O comes in. cheers -ben > > > On 2018-10-07, at 1:11 AM, Ben Coman <btc(a)openinworld.com> wrote: > > > > Cross posting since at this level systems are still very similar. > > > > I've sometimes wondered about how the idle process > > relinquishing the CPU interacted with delay scheduling, > > since they operate at the extreme opposite ends of process priorities. > > > > Historically there was... > > ProcessorScheduler class >> idleProcess > > [ "A default background process which is invisible." > > [true] whileTrue: > > [self relinquishProcessorForMicroseconds: 1000] > > > > which had the following performance this for later comparison... > > (1 to: 10) collect: [:i | [ (Delay forMilliseconds: 1) wait ] > timeToRun asMilliSeconds]. > > ==> "#(2 5 4 2 4 4 2 4 4 3)" > > > > To improve battery life yield time Pharo changed this to 50000 in... > > * > https://pharo.fogbugz.com/f/cases/20425/Yield-longer-in-ProcessorScheduler-… > > * https://github.com/pharo-project/pharo/commit/0b0d12dc > > but had a negative impact on delays... > > (1 to: 10) collect: [:i | [ (Delay forMilliseconds: 1) wait ] > timeToRun asMilliSeconds]. > > ==> "#(36 51 50 51 50 51 51 30 50 50)" > > as reported... > https://pharo.fogbugz.com/f/cases/22400/Delays-are-not-working-properly > > > > The problem seems to be that #relinquishProcessorForMicroseconds: > suspends the main VM thread for a fixed amount during which expired delays > cannot be dealt with. I'm not sure of the exact mechanism in the VM but > this looks related... > > Win: > https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/e2fa2d1/platforms/wi… > > Mac: > https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/a8a1dc1/platforms/un… > > I'm not sure about Linux > > > > One idea was to have a setting, but another path is to mix the > idle-relinquish > > into the delay-scheduling to dynamically relinquish up to exactly when > the activeDelay expires. > > > > After loading... > > https://github.com/pharo-project/pharo/pull/1887 > > you can do... > > DelayIdleTicker installExperiment. > > (1 to: 10) collect: [:i | [ (Delay forMilliseconds: 1) wait ] > timeToRun asMilliSeconds]. > > ==>"#(1 1 2 2 2 2 2 2 2 2)" which btw is half the latency of the original > > DelayIdleTicker debug: true. "CPU usage goes way up" > > DelayIdleTicker uninstall. > > > > I'm now seeking: > > * comment on how this might interact with parts of the VM I'm not > familiar with. > > * help to discover and stress test corner cases. > > * help to determine if there actually is a benefit and characterize what > that is, > > especially anyone familiar with headless images with reduced UI and I/O > events. > > I was surprised to see the existing system already often showed 0% CPU > usage (in Windows). > > > > cheers -ben > > > > > tim > -- > tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim > Bayard(n): a person armed with the self-confidence of ignorance > > >

1 0

[Pharo 7.0-dev] Build #1315: 22539 Tag ManifestRPackageCore and related classes in RPackage-Core
by ci-pharo-ci-jenkins2＠inria.fr Oct. 7, 2018

Oct. 7, 2018

There is a new Pharo build available! The status of the build #1315 was: SUCCESS. The Pull Request #1877 was integrated: "22539 Tag ManifestRPackageCore and related classes in RPackage-Core" Pull request url: https://github.com/pharo-project/pharo/pull/1877 Issue Url: https://pharo.fogbugz.com/f/cases/22539 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1314: 20344-DualChangeSorter-shows-debug-context-menu
by ci-pharo-ci-jenkins2＠inria.fr Oct. 7, 2018

Oct. 7, 2018

There is a new Pharo build available! The status of the build #1314 was: SUCCESS. The Pull Request #1881 was integrated: "20344-DualChangeSorter-shows-debug-context-menu" Pull request url: https://github.com/pharo-project/pharo/pull/1881 Issue Url: https://pharo.fogbugz.com/f/cases/20344 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1313: 22546 Tag classes in FuzzyMatcher-Tests
by ci-pharo-ci-jenkins2＠inria.fr Oct. 7, 2018

Oct. 7, 2018

There is a new Pharo build available! The status of the build #1313 was: SUCCESS. The Pull Request #1885 was integrated: "22546 Tag classes in FuzzyMatcher-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/1885 Issue Url: https://pharo.fogbugz.com/f/cases/22546 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1312: 22544 Comment File package
by ci-pharo-ci-jenkins2＠inria.fr Oct. 7, 2018

Oct. 7, 2018

There is a new Pharo build available! The status of the build #1312 was: FAILURE. The Pull Request #1883 was integrated: "22544 Comment File package" Pull request url: https://github.com/pharo-project/pharo/pull/1883 Issue Url: https://pharo.fogbugz.com/f/cases/22544 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0