- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #217: 20562-BaselineOfMorphic-should-include-System-Localization
by ci-pharo-ci-jenkins2＠inria.fr Oct. 21, 2017

Oct. 21, 2017

There is a new Pharo build available! The status of the build #217 was: SUCCESS. The Pull Request #382 was integrated: "20562-BaselineOfMorphic-should-include-System-Localization" Pull request url: https://github.com/pharo-project/pharo/pull/382 Issue Url: https://pharo.fogbugz.com/f/cases/20562 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Launcher: VM Problem
by Sean P. DeNigris Oct. 20, 2017

Oct. 20, 2017

I have a recent working VM in ~/Documents/Pharo/vms/60. Instead of using it, the last Launcher release downloaded another one to ~/Documents/Pharo/vms/60-x86. However, this seems to be an older one which does not support Iceberg (I get a message about outdated libgit). Per the System Reporter: ~/Documents/Pharo/vms/60-x86/Pharo.app/Contents/MacOS/Pharo CoInterpreter VMMaker.oscog-eem.2231 uuid: de62947a-7f40-4977-a232-e06a3a80c939 May 31 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2227 uuid: 7ea146b4-39ce-4de7-afa3-a76ed1d1da35 May 31 2017 VM: 201705310241 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Tue May 30 19:41:27 2017 -0700 $ Plugins: 201705310241 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

3 3

[Pharo 7.0-dev] Build #216: 20471-Tests-for-Unicode-Categories-are-missing
by ci-pharo-ci-jenkins2＠inria.fr Oct. 20, 2017

Oct. 20, 2017

There is a new Pharo build available! The status of the build #216 was: SUCCESS. The Pull Request #326 was integrated: "20471-Tests-for-Unicode-Categories-are-missing" Pull request url: https://github.com/pharo-project/pharo/pull/326 Issue Url: https://pharo.fogbugz.com/f/cases/20471 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #215: 19105-Default-time-limit-for-tests-should-be-really-small
by ci-pharo-ci-jenkins2＠inria.fr Oct. 20, 2017

Oct. 20, 2017

There is a new Pharo build available! The status of the build #215 was: SUCCESS. The Pull Request #71 was integrated: "19105-Default-time-limit-for-tests-should-be-really-small" Pull request url: https://github.com/pharo-project/pharo/pull/71 Issue Url: https://pharo.fogbugz.com/f/cases/19105 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #214: 19572--should-be-a-compile-time-selector
by ci-pharo-ci-jenkins2＠inria.fr Oct. 20, 2017

Oct. 20, 2017

There is a new Pharo build available! The status of the build #214 was: SUCCESS. The Pull Request #70 was integrated: "19572--should-be-a-compile-time-selector" Pull request url: https://github.com/pharo-project/pharo/pull/70 Issue Url: https://pharo.fogbugz.com/f/cases/19572 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Anoying bug fond in Artefact running in Windows 10
by casimiro barreto Oct. 20, 2017

Oct. 20, 2017

6.1 32 bits. Windows 10 pro... Em 20 de out de 2017 3:40 AM, "olivier auverlot" <olivier.auverlot(a)gmail.com> escreveu: Hi Casimiro, Which version of Pharo do you use ? 6.1 ? Olivier :) 2017-10-19 18:27 GMT+02:00 <casimiro.barreto(a)gmail.com>: > When you insert a jpeg from a file, for some reason the file descriptor > (stream) is kept open (at least in the Windows end of things). Then, if a > second page is to be generated, the following error is shown: > > 'MessageNotUnderstood: receiver of "reset" is nil > > PDFJpegElement>>stream: > JPEGReadWriter > aJPEGReadWriter > JPEGReadWriter(ImageReadWriter)>>on: > nil > > Sample code: > > aPage := PDFPage new. > > imageStream := FileStream fileNamed: 'lsi-tec.jpg'. > > aPage > add: > ((PDFJpegElement fromStream: imageStream) > from: 15 mm @ 20 mm; > dimension: 40 mm @ 40 mm). > imageStream close. > > Generated report is in annex > > The only way to recover is to close pharo, start it again. Then the file > descriptor (stream) is released and it is possible to go on. > > Has anyone faced this problem? > How to solve it? > > Best regards, > > Casimiro Barreto > >

1 0

[Pharo 7.0-dev] Build #213: 20228-Checking if the directory is empty before delete.
by ci-pharo-ci-jenkins2＠inria.fr Oct. 20, 2017

Oct. 20, 2017

There is a new Pharo build available! The status of the build #213 was: SUCCESS. The Pull Request #375 was integrated: "20228-Checking if the directory is empty before delete." Pull request url: https://github.com/pharo-project/pharo/pull/375 Issue Url: https://pharo.fogbugz.com/f/cases/20228 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #212: Disable concurrent builds of development branch
by ci-pharo-ci-jenkins2＠inria.fr Oct. 20, 2017

Oct. 20, 2017

There is a new Pharo build available! The status of the build #212 was: SUCCESS. The Pull Request #363 was integrated: "Disable concurrent builds of development branch" Pull request url: https://github.com/pharo-project/pharo/pull/363 Issue Url: https://pharo.fogbugz.com/f/cases/20541 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

CI Build order and strange "latest" Pharo 7 effect
by Torsten Bergmann Oct. 20, 2017

Oct. 20, 2017

Hi, today there was an interesting effect visible for the Pharo build on CI for Pharo 7: Esteban merged three contributions for Pharo 7 into #development (see [1]). All three merges on git triggered the CI. For each a separate build for Pharo 7 started on CI independently. While usually one would expect the builds in regular build order 183, 184, 185 the CI job for building 185 job was faster (as you can see on the attached screenshot). So the 185 series of images was copied first to the file server [3] because the job was already finished. Afterwards 183 build completed on CI and these images were copied to the file server with a newer timestamp. So you have the order 185, 183 with 183 having the files with the newest timestamp (but not being the most recent state of Pharo). This leads to several unfortunate effects: 1. When you sort on file server [3] descending by date the build 183 images are newer than the build 185 images 2. When you use PharoLauncher to download "latest-32" you get an 183 image instead of the "real latest" 185 image 3. When you ask Zeroconf to download the latest using http://get.pharo.org/70+vm you also get 183 instead of the already available 185 So as the CI build of an older "update" (here 183) finished later than the most recent version (here 185) you get 183 as "latest" instead of 185. Any ideas how we could avoid such a side effect? Maybe a chain on the builds so 183 has to finished before 184 and 185 could be built? Thx T. [1] https://github.com/pharo-project/pharo/commits/development [2] https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… [3] http://files.pharo.org/image/70/

4 8

[Pharo 7.0-dev] Build #211: 20558-Spec-tests-still-use-Model-suffix
by ci-pharo-ci-jenkins2＠inria.fr Oct. 20, 2017

Oct. 20, 2017

There is a new Pharo build available! The status of the build #211 was: SUCCESS. The Pull Request #380 was integrated: "20558-Spec-tests-still-use-Model-suffix" Pull request url: https://github.com/pharo-project/pharo/pull/380 Issue Url: https://pharo.fogbugz.com/f/cases/20558 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0