- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #338: 20769-DateAndTime-now-returns-summer-time-in-winter-France-time-zone
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2017

Nov. 27, 2017

There is a new Pharo build available! The status of the build #338 was: FAILURE. The Pull Request #553 was integrated: "20769-DateAndTime-now-returns-summer-time-in-winter-France-time-zone" Pull request url: https://github.com/pharo-project/pharo/pull/553 Issue Url: https://pharo.fogbugz.com/f/cases/20769 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #337: 19304-anyOne-comment-should-be-improved
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2017

Nov. 27, 2017

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

1 0

Re: [Pharo-dev] Is SmalltalkCI working for Pharo projects?
by Aliaksei Syrel Nov. 27, 2017

Nov. 27, 2017

Hi, We have the same problem. It infinitly loops on coverage and says "out of memory" in the end. Cheers, Alex On Nov 26, 2017 2:18 PM, "Gabriel Cotelli" <g.cotelli(a)gmail.com> wrote: I'm pretty sure are not my changes, because in one of the pull requests I just added Pharo 6.1 as a tested platform but no code was changed and I'm getting the same error on all the platforms ( https://github.com/ba-st/Buoy/ pull/18 ). Fabio: maybe something changed in SmalltalkCI triggering this error? From the logs seems that it's something related to coverage doing an infinite loop: IdentityDictionary(HashedCollection)>findElementOrNil: 0xc089d50: a(n) IdentityDictionary 0xfff87dd4 M IdentityDictionary(Dictionary)>at:ifAbsent: 0xc089d50: a(n) IdentityDictionary 0xfff87df4 M RGMethodDefinition(RGDefinition)>annotationNamed:ifAbsent: 0xc083658: a(n) RGMethodDefinition 0xfff87e14 M RGMethodDefinition(RGDefinition)>environment 0xc083658: a(n) RGMethodDefinition 0xfff87e30 M RGMethodDefinition(RGDefinition)>rootEnvironment 0xc083658: a(n) RGMethodDefinition 0xfff87e48 M RGMethodDefinition(RGElementDefinition)>realParent 0xc083658: a(n) RGMethodDefinition 0xfff87e60 M RGMethodDefinition(RGElementDefinition)>realClass 0xc083658: a(n) RGMethodDefinition 0xfff87e78 M RGMethodDefinition(RGElementDefinition)>actualClass 0xc083658: a(n) RGMethodDefinition 0xfff87e90 M TestCoverage>uninstall 0xc082400: a(n) TestCoverage 0xfff87ea8 M TestCoverage>run:with:in: 0xc082400: a(n) TestCoverage 0xfff87ecc M ByteString(String)>asSymbol 0x9300760: a(n) ByteString 0xfff87ef0 M SystemDictionary>classOrTraitNamed: 0x9895350: a(n) SystemDictionary 0xfff87f0c M SystemDictionary>classNamed: 0x9895350: a(n) SystemDictionary 0xfff87f28 M RGMethodDefinition(RGElementDefinition)>realParent 0xc083658: a(n) RGMethodDefinition 0xfff87f40 M RGMethodDefinition(RGElementDefinition)>realClass 0xc083658: a(n) RGMethodDefinition 0xfff87f58 M RGMethodDefinition(RGElementDefinition)>actualClass 0xc083658: a(n) RGMethodDefinition 0xfff87f70 M TestCoverage>uninstall 0xc082400: a(n) TestCoverage 0xfff87f88 M TestCoverage>run:with:in: 0xc082400: a(n) TestCoverage 0xfff87fac M ByteString(String)>asSymbol 0x9300780: a(n) ByteString 0xfff87fd0 M SystemDictionary>classOrTraitNamed: 0x9895350: a(n) SystemDictionary 0xfff87fec M SystemDictionary>classNamed: 0x9895350: a(n) SystemDictionary 0xfff88008 M RGMethodDefinition(RGElementDefinition)>realParent 0xc083658: a(n) RGMethodDefinition 0xfff88020 M RGMethodDefinition(RGElementDefinition)>realClass 0xc083658: a(n) RGMethodDefinition 0xfff88038 M RGMethodDefinition(RGElementDefinition)>actualClass 0xc083658: a(n) RGMethodDefinition 0xfff88050 M TestCoverage>uninstall 0xc082400: a(n) TestCoverage 0xfff88068 M TestCoverage>run:with:in: 0xc082400: a(n) TestCoverage 0xfff8808c M ByteString(String)>asSymbol 0x93007a0: a(n) ByteString 0xfff880b0 M SystemDictionary>classOrTraitNamed: 0x9895350: a(n) SystemDictionary 0xfff880cc M SystemDictionary>classNamed: 0x9895350: a(n) SystemDictionary 0xfff880e8 M RGMethodDefinition(RGElementDefinition)>realParent 0xc083658: a(n) RGMethodDefinition 0xfff88100 M RGMethodDefinition(RGElementDefinition)>realClass 0xc083658: a(n) RGMethodDefinition 0xfff88118 M RGMethodDefinition(RGElementDefinition)>actualClass 0xc083658: a(n) RGMethodDefinition 0xfff88130 M TestCoverage>uninstall 0xc082400: a(n) TestCoverage 0xfff88148 M TestCoverage>run:with:in: 0xc082400: a(n) TestCoverage 0xfff8816c M ByteString(String)>asSymbol 0x93007c0: a(n) ByteString 0xfff88190 M SystemDictionary>classOrTraitNamed: 0x9895350: a(n) SystemDictionary 0xfff881ac M SystemDictionary>classNamed: 0x9895350: a(n) SystemDictionary 0xfff85e48 M RGMethodDefinition(RGElementDefinition)>realParent 0xc083658: a(n) RGMethodDefinition 0xfff85e60 M RGMethodDefinition(RGElementDefinition)>realClass 0xc083658: a(n) RGMethodDefinition 0xfff85e78 M RGMethodDefinition(RGElementDefinition)>actualClass 0xc083658: a(n) RGMethodDefinition 0xfff85e90 M TestCoverage>uninstall 0xc082400: a(n) TestCoverage 0xfff85ea8 M TestCoverage>run:with:in: 0xc082400: a(n) TestCoverage On Nov 26, 2017 06:00, "Ben Coman" <btc(a)openinworld.com> wrote: The Raw Log of https://travis-ci.org/ba-st/Willow/jobs/307025742 says "The log length has exceeded the limit of 4 MB (this usually means that the test suite is raising the same exception over and over)." whereas the Raw Log from a working job https://travis-ci.org/ba-st/Wi llow/jobs/303028020 is 94kB. So you might start with some side-by-side diff tool to observe where these log files diverge. cheers -ben On 26 November 2017 at 03:40, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > All the latest builds I've tried are failing in Travis with "out of > memory" errors aparently after running the tests. It's always the same > error and for different Pharo versions (4.0 5.0 6.1 7.0 , etc) > > See for example https://travis-ci.org/ba-st/Willow/jobs/307025742 > > Anyone noticed something similar? > > Regards, > Gabriel >

2 2

[Pharo 7.0-dev] Build #336: 20768-remove-GLMWatcherMorphicTest
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2017

Nov. 27, 2017

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

1 0

[Pharo 7.0-dev] Build #335: 20758-Slot-should-have-explicit-property-definingClass2
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2017

Nov. 27, 2017

There is a new Pharo build available! The status of the build #335 was: SUCCESS. The Pull Request #543 was integrated: "20758-Slot-should-have-explicit-property-definingClass2" Pull request url: https://github.com/pharo-project/pharo/pull/543 Issue Url: https://pharo.fogbugz.com/f/cases/20758 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #334: 20766-Increase-priority-of-FreeType-initialization
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2017

Nov. 27, 2017

There is a new Pharo build available! The status of the build #334 was: SUCCESS. The Pull Request #548 was integrated: "20766-Increase-priority-of-FreeType-initialization" Pull request url: https://github.com/pharo-project/pharo/pull/548 Issue Url: https://pharo.fogbugz.com/f/cases/20766 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #333: 20699-Convenience-method-for-creating-typed-buffers-to-pass-by-ref-through-FFI-
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2017

Nov. 27, 2017

There is a new Pharo build available! The status of the build #333 was: SUCCESS. The Pull Request #508 was integrated: "20699-Convenience-method-for-creating-typed-buffers-to-pass-by-ref-through-FFI-" Pull request url: https://github.com/pharo-project/pharo/pull/508 Issue Url: https://pharo.fogbugz.com/f/cases/20699 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Iceberg operations overview
by Pavel Krivanek Nov. 27, 2017

Nov. 27, 2017

Hi, during brainstorming of the Iceberg UI simplification we created a document that shows what the current Iceberg operations do. It should help you to clarify the role of the working copy etc. See the attachment. Note: merge uses the reference commit of the loaded version as the base. Cheers, -- Pavel

4 3

Esteban's ChangeLog week of 20 November 2017
by estebanlm＠gmail.com Nov. 27, 2017

Nov. 27, 2017

Hello! This is my weekly ChangeLog, from 20 November 2017 to 26 November 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=20/11/2017&to=26/11/2017 ChangeLog ========= 24 November 2017: ----------------- * I spent some time working on the health of CI for some projects. So far, I restored the green status to: * [Tonel](https://github.com/pharo-vcs/tonel) * [Libgit2-bindings](https://github.com/pharo-vcs/libgit2-pharo-bindings) Now I need to work on the hardest (and most important) one: [Iceberg](https://github.com/pharo-vcs/iceberg) Some of this broken status were because we needed a functionality on smalltalkCI who was missing: the ability to execute some scripts before loading, and we need to cleanup the images (since I am testing things that are already there). Now, thanks to Fabio is fixed so we can move on. 23 November 2017: ----------------- * after spend last two days fixing bugs on the parser, I finally could integrate * Iceberg 0.6.3 * Tonel 1.0.4 * Libgit2-bindings 1.0 Into Pharo 7.0a. Now... I need to prepare an update to backport to Pharo 6.1. 21 November 2017: ----------------- * I released iceberg version [0.6.3](https://github.com/pharo-vcs/iceberg/releases/tag/v0.6.3) . And I released also tonel version [1.0.4](https://github.com/pharo-vcs/tonel/releases/tag/v1.0.4) Along, that will bring a better iceberg for everybody ;) (now I need to integrate to Pharo 7.0a and backport to 6.1) 20 November 2017: ----------------- * Back from holidays. During my freetime, I worked on Iceberg a bit... there was an ugly bug, [commit&push can lead to lose data](https://github.com/pharo-vcs/iceberg/issues/516) and fix it took more time than expected. Now is done, I will prepare a release today with some other issues. cheers! Esteban

1 0

Pharo 32bit on debian 9 stretch 64bit
by Cyril Ferlicot Nov. 26, 2017

Nov. 26, 2017

Hi, I would like to use Pharo on a Debian 9, 64bits. On Pharo website there is an explanation of the requirements for Debian 7 and 8. For Debian it is: sudo dpkg --add-architecture i386 sudo apt-get update sudo apt-get install libx11-6:i386 sudo apt-get install libgl1-mesa-glx:i386 sudo apt-get install libfontconfig1:i386 sudo apt-get install libssl1.0.0:i386 The problem is that sudo apt-get install libssl1.0.0:i386 throw me this error: Reading package lists... Done Building dependency tree Reading state information... Done Package libssl1.0.0:i386 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'libssl1.0.0:i386' has no installation candidate Pharo cannot be use with this libssl. I think that Pharo's webstie should also cover Debian 9. Does someone know what should I do to get the right dependencies? Should I manually download the .deb of debian 8 and install it? -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

3 3