November 2017 - Pharo-dev - lists.pharo.org

Problem with primitive instVarAt: / instVarAt:put:, what should we do ?
by ClÃ©ment Bera Nov. 28, 2017

Nov. 28, 2017

Hi All, It seems Pharo is lacking the slotAt: / slotAt:put: primitive and that the instVarAt: / instVarAt:put: primitive is not doing what it says it does. When I look at Object>>#instVarAt: I see: "[...]Answer a fixed variable in an object. The numbering of the variables corresponds to the named instance variables, followed by the indexed instance variables. Fail if the index is not an Integer or is not the index of a fixed variable[...]" Now in Pharo 7 when one does: #(iv1) instVarAt: 1, one gets #iv1. So the comment is wrong. The reason for this is that instVarAt: / instVarAt:put: should be primitive 73/74, while they are in Pharo 173/174 (primitive slotAt:/slotAt:put:). The slot primitive access pointer slots of objects, whichever inst var or variable fields. A good example would be: | t | t := #temp. [ t ] instVarAt: 4, one gets #temp So I have two solutions for this problem: 1) We change the instVarAt: / instVarAt:put: primitives comments to match the slotAt: / slotAt:put: behavior, and in Pharo instVarAt: / instVarAt:put: means in factslotAt: / slotAt:put: . 2) We change the instVarAt: / instVarAt:put: primitives to primitive 73 and 74, we introduce slotAt: / slotAt:put: with primitive 173/174 and we ask everyone to fix their code relying on instVarAt: / instVarAt:put: acting as slotAt: / slotAt:put: What do you think ? Best, -- ClÃ©ment BÃ©ra Pharo consortium engineer https://clementbera.wordpress.com/ BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq

7 13

[Pharo 7.0-dev] Build #343: 20772 - Unused temps in MBConfigurationInfo, MethodDictionaryTest, ...
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 #343 was: FAILURE. The Pull Request #557 was integrated: "20772 - Unused temps in MBConfigurationInfo, MethodDictionaryTest,..." Pull request url: https://github.com/pharo-project/pharo/pull/557 Issue Url: https://pharo.fogbugz.com/f/cases/20772 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #342: 20745-cleanup-unused-methods-OCOptimizedBlockScope
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 #342 was: SUCCESS. The Pull Request #556 was integrated: "20745-cleanup-unused-methods-OCOptimizedBlockScope" Pull request url: https://github.com/pharo-project/pharo/pull/556 Issue Url: https://pharo.fogbugz.com/f/cases/20745 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #341: 20700-translateToUTC-does-not-work-on-Month-and-Year
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 #341 was: SUCCESS. The Pull Request #545 was integrated: "20700-translateToUTC-does-not-work-on-Month-and-Year" Pull request url: https://github.com/pharo-project/pharo/pull/545 Issue Url: https://pharo.fogbugz.com/f/cases/20700 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #340: 20770-Open-WelcomeHelp-window-at-startup
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 #340 was: SUCCESS. The Pull Request #555 was integrated: "20770-Open-WelcomeHelp-window-at-startup" Pull request url: https://github.com/pharo-project/pharo/pull/555 Issue Url: https://pharo.fogbugz.com/f/cases/20770 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #339: 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 #339 was: SUCCESS. 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 #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