- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #531: Use Integer literal to avoid Float in GemStone

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

There is a new Pharo build available! The status of the build #531 was: FAILURE. The Pull Request #4013 was integrated: "Use Integer literal to avoid Float in GemStone" Pull request url: https://github.com/pharo-project/pharo/pull/4013 Issue Url: https://github.com/pharo-project/pharo/issues/DateAndTime_class_now Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 19, 2019

[Pharo 8.0] Build #529: 4001-BehaviorparseTreeFor-should-call-parseTree-on-CompiledMethod

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

There is a new Pharo build available! The status of the build #529 was: FAILURE. The Pull Request #4009 was integrated: "4001-BehaviorparseTreeFor-should-call-parseTree-on-CompiledMethod" Pull request url: https://github.com/pharo-project/pharo/pull/4009 Issue Url: https://github.com/pharo-project/pharo/issues/4001 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 18, 2019

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

by Ronie Salgado

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 18, 2019

linux minheadless pharo vm builds itimer or heartbeat?

by Alistair Grant

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 18, 2019

[Pharo 8.0] Build #528: Remove-code-in-baselines-related-to-old-pharo-versions

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

There is a new Pharo build available! The status of the build #528 was: SUCCESS. The Pull Request #3988 was integrated: "Remove-code-in-baselines-related-to-old-pharo-versions" Pull request url: https://github.com/pharo-project/pharo/pull/3988 Issue Url: https://github.com/pharo-project/pharo/issues/Remove Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 18, 2019

[Pharo 8.0] Build #527: ifNil usage on GT packages

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

There is a new Pharo build available! The status of the build #527 was: FAILURE. The Pull Request #3972 was integrated: "ifNil usage on GT packages" Pull request url: https://github.com/pharo-project/pharo/pull/3972 Issue Url: https://github.com/pharo-project/pharo/issues/ifNilOnGT Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 18, 2019

[Pharo 8.0] Build #526: Deprecation related improvements

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

There is a new Pharo build available! The status of the build #526 was: FAILURE. The Pull Request #3997 was integrated: "Deprecation related improvements" Pull request url: https://github.com/pharo-project/pharo/pull/3997 Issue Url: https://github.com/pharo-project/pharo/issues/deprecations Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 18, 2019

[Pharo 8.0] Build #525: ifNil usage on packages starting with R

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

There is a new Pharo build available! The status of the build #525 was: FAILURE. The Pull Request #3981 was integrated: "ifNil usage on packages starting with R" Pull request url: https://github.com/pharo-project/pharo/pull/3981 Issue Url: https://github.com/pharo-project/pharo/issues/ifNilOnRPackages Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 18, 2019

[Pharo 8.0] Build #524: Changed some Fuel code sending messages deprecated in Pharo 7

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

There is a new Pharo build available! The status of the build #524 was: SUCCESS. The Pull Request #3987 was integrated: "Changed some Fuel code sending messages deprecated in Pharo 7" Pull request url: https://github.com/pharo-project/pharo/pull/3987 Issue Url: https://github.com/pharo-project/pharo/issues/deprecated70 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 18, 2019

[Pharo 8.0] Build #523: Hint GH language parser on .st files

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

There is a new Pharo build available! The status of the build #523 was: SUCCESS. The Pull Request #3994 was integrated: "Hint GH language parser on .st files" Pull request url: https://github.com/pharo-project/pharo/pull/3994 Issue Url: https://github.com/pharo-project/pharo/issues/patch Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 18, 2019