July 2019 - Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #537: 4003-add-inspector-for-all-defined-ClassVariables

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

There is a new Pharo build available! The status of the build #537 was: FAILURE. The Pull Request #4010 was integrated: "4003-add-inspector-for-all-defined-ClassVariables" Pull request url: https://github.com/pharo-project/pharo/pull/4010 Issue Url: https://github.com/pharo-project/pharo/issues/4003 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 21, 2019

[Pharo 8.0] Build #536: Fixed several code critics on the `Tests` package

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

There is a new Pharo build available! The status of the build #536 was: FAILURE. The Pull Request #4023 was integrated: "Fixed several code critics on the `Tests` package" Pull request url: https://github.com/pharo-project/pharo/pull/4023 Issue Url: https://github.com/pharo-project/pharo/issues/fixedCodeCriticsOnTestsPackage Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 21, 2019

Re: [Pharo-dev] [Vm-dev] linux minheadless pharo vm builds itimer or heartbeat?

by Alistair Grant

Hi Ronie, Thanks for your update. I haven't looked at the directory structure, but the idea of using minheadless as the core makes sense. Thanks again, Alistair On Thu, 18 Jul 2019 at 16:56, Ronie Salgado <roniesalg(a)gmail.com> wrote: > > > Hi Alistair, > > That is a bug that I have to fix. Currently, it is only using and old version of the threaded heartbeat. This because of the intentional duplication of code that I did originally when doing the minheadless VM: > 1.- Remove everything. > 2.- Stub all of the platform specific code > 3.- Compile and fix linking errors by adding the platform specific code. > > Now the missing step is to remove this code duplication by merging the code of the minheadless VM with the normal VM. The main problem of fixing this is that I will need to coordinate with the rest of the VM community on what is the best course of action. In my opinion, I think that the correct way for doing this is to use the minheadless VM as the core VM, and support the different windowing systems by refactoring the code in folders under the platforms/minheadless/ > > Best regards, > Ronie > > El jue., 18 jul. 2019 a las 10:11, Alistair Grant (<akgrant0710(a)gmail.com>) escribiÃ³: >> >> >> Hi All, >> >> Are Pharo linux minheadless builds itimer or threaded heartbeat? >> >> (all the listings below are extracts, not the complete file / page) >> >> The file list on bintray suggests that they are itimer: >> >> https://bintray.com/opensmalltalk/vm/cog/201907112020#files >> >> pharo.cog.spur+sdl2-cmake-minhdls_linux64x64_itimer_201907112020.tar.gz >> 6 days ago 4.23 MB >> pharo.cog.spur-cmake-minhdls_linux64x64_itimer_201907112020.tar.gz 6 >> days ago 4.22 MB >> >> >> While travis indicates that only threaded heartbeat versions are built: >> >> https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/builds/553922116 >> >> Setting environment variables from .travis.yml >> $ export ARCH="linux64x64" >> $ export FLAVOR="pharo.cog.spur" >> $ export CPU_ARCH="x64" >> $ export HEARTBEAT="threaded" >> $ export BUILD_WITH_CMAKE="yes" >> >> >> .travis.yml agrees with the travis output: >> >> - stage: "Minheadless CMake builds" >> - env: ARCH="linux32x86" FLAVOR="pharo.cog.spur" CPU_ARCH="x86" >> HEARTBEAT="threaded" BUILD_WITH_CMAKE="yes" >> - env: ARCH="linux64x64" FLAVOR="pharo.cog.spur" CPU_ARCH="x64" >> HEARTBEAT="threaded" BUILD_WITH_CMAKE="yes" >> >> >> And pack-vm.sh seems to be doing the right thing when determining how >> to name the archive: >> >> for dir in */; do >> if [[ "${ARCH}" == *"ARM"* || "${dir}" == *"ht/" ]]; then >> name="${IDENTIFIER}" >> else >> name="${IDENTIFIER_ITIMER}" >> fi >> >> >> Unfortunately figuring out which VM is being used isn't helped by the >> fact that "pharo --version" doesn't work with minheadless: >> >> $ ./pharo --version >> Opening Image: --version >> Opening Image: No such file or directory >> Error opening image file: --version >> >> >> Thanks, >> Alistair

July 21, 2019

[Pharo 8.0] Build #535: SUCCESS

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

There is a new Pharo build available! The status of the build #535 was: SUCCESS. Could not extract further issue information from commit message: Delete weekly-digest.yml remove weekly digest config as it did not run yesterday Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 21, 2019

Re: [Pharo-dev] [Blog Post] PoC Alpine Linux Minimal Stateless Pharo

by Pierce Ng

On Sat, Jul 20, 2019 at 10:58:36AM -0300, Mariano Martinez Peck wrote: > This is very interesting. I have been playing with docker too [1] [2] [3] > and indeed I also tried to make it work with alpine [4]. But it was Hi Mariano, Fun stuff! > Anyway, I will be curious to know your progress. Would cog VM work > correctly with musl instead of glibc? That's what I'll find out. :-) I built the Cog VM from source on Alpine. As written in my post said Cog VM successfully runs a minimal Pharo image doing FFI and Fuel. I'll be testing it with the regular image running some kind of webapp. Pierce

July 21, 2019

Re: [Pharo-dev] [Blog Post] PoC Alpine Linux Minimal Stateless Pharo

by Mariano Martinez Peck

Hi Pierce, Cross posting my answer from VM to here, sorry for the duplicate. This is very interesting. I have been playing with docker too [1] [2] [3] and indeed I also tried to make it work with alpine [4]. But it was complicated because alpine doesn't come with `glibc` but instead `musl`. And there are differences between them. So for example for VA Smalltalk I had to install `glibc`. I succeeded but the final size of the docker image with alpine + glibc was almost the same size as the debian lite... so it didn't make much sense to me. The support for glic is not official and as you can see I reported it [5] Anyway, I will be curious to know your progress. Would cog VM work correctly with musl instead of glibc? Best, [1] https://dev.to/martinezpeck/getting-started-with-docker-and-smalltalk-4po1 [2] https://dev.to/martinezpeck/step-2-single-node-docker-swarm-and-smalltalk-4… [3] https://dev.to/martinezpeck/docker-swarm-cloud-on-a-arm64-diy-sbc-cluster-r… <https://dev.to/martinezpeck/docker-swarm-cloud-on-a-arm64-diy-sbc-cluster-r…> [4] https://github.com/vasmalltalk/docker-examples/blob/master/source/SeasideTr… [5] https://github.com/sgerrand/alpine-pkg-glibc/issues/113 On Sat, Jul 20, 2019 at 5:39 AM Pierce Ng <pierce(a)samadhiweb.com> wrote: > Hi all, > > I've written a blog post on the topic. > > https://www.samadhiweb.com/blog/2019.07.20.alpine.pharo.minimal.html > > TL;DR: > > - Built pharo.cog.spur.minheadless on Alpine Linux. > > - Built Docker image of same: 12.5MB. > > - Using 7-minimal as base, built a stateless Pharo image with SUnit and > SQLite: ~16MB. > > - Ran the SQLite unit tests from the command line using said > image statelessly. > > - Built Docker image of Alpine Pharo VM and a/m SQLite Pharo image: 46.8MB. > > - Ran said Docker image which ran the SQLite unit tests. > > Pierce > > -- Mariano Martinez Peck Email: marianopeck(a)gmail.com Twitter: @MartinezPeck LinkedIn: www.linkedin.com/in/mariano-martinez-peck <https://www.linkedin.com/in/mariano-mart%C3%ADnez-peck/> Blog: https://marianopeck.wordpress.com/

July 20, 2019

[Blog Post] PoC Alpine Linux Minimal Stateless Pharo

by Pierce Ng

Hi all, I've written a blog post on the topic. https://www.samadhiweb.com/blog/2019.07.20.alpine.pharo.minimal.html TL;DR: - Built pharo.cog.spur.minheadless on Alpine Linux. - Built Docker image of same: 12.5MB. - Using 7-minimal as base, built a stateless Pharo image with SUnit and SQLite: ~16MB. - Ran the SQLite unit tests from the command line using said image statelessly. - Built Docker image of Alpine Pharo VM and a/m SQLite Pharo image: 46.8MB. - Ran said Docker image which ran the SQLite unit tests. Pierce

July 20, 2019

[Pharo 8.0] Build #534: Change some isNil ifTrue: and variants to use ifNil: and friends.

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

There is a new Pharo build available! The status of the build #534 was: FAILURE. The Pull Request #4018 was integrated: "Change some isNil ifTrue: and variants to use ifNil: and friends." Pull request url: https://github.com/pharo-project/pharo/pull/4018 Issue Url: https://github.com/pharo-project/pharo/issues/ifNilUsageImprovements Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 20, 2019

[ANN] Next Pharo Sprint: July 27

by Marcus Denker

We will organize a Pharo sprint / Moose dojo July 27, starting at 10:00am. (Local Time Paris). Goals of this sprint: - Pharo 8: Fix issues from tracker https://github.com/pharo-project/pharo/issues <https://github.com/pharo-project/pharo/issues> Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events <http://pharo.org/contribute-events> We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 <https://github.com/orgs/pharo-project/projects/9> Known Local Sprint meetings - Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come A list of all Pharo Event of the year an be found here: https://association.pharo.org/events <https://association.pharo.org/events>

July 19, 2019

[Pharo 7.0] Build #165: [Backport] Fix for #3410-[Trait] Impossible to use from a classTrait a method that is also defined in a subclass of Behavior even when following the doc

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

There is a new Pharo build available! The status of the build #165 was: FAILURE. The Pull Request #3906 was integrated: "[Backport] Fix for #3410-[Trait] Impossible to use from a classTrait a method that is also defined in a subclass of Behavior even when following the doc" Pull request url: https://github.com/pharo-project/pharo/pull/3906 Issue Url: https://pharo.fogbugz.com/f/cases/FIX/Backportof#3410 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 19, 2019