- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #337: 19304-anyOne-comment-should-be-improved

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

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…

Nov. 27, 2017

Re: [Pharo-dev] Is SmalltalkCI working for Pharo projects?

by Gabriel Cotelli

Fabio fixed it. Aliaksei please try restarting your failing builds. On Sun, Nov 26, 2017 at 11:13 AM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > 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 >> > > > >

Nov. 27, 2017

[Pharo 7.0-dev] Build #336: 20768-remove-GLMWatcherMorphicTest

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

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…

Nov. 27, 2017

[Pharo 7.0-dev] Build #335: 20758-Slot-should-have-explicit-property-definingClass2

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

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…

Nov. 27, 2017

Re: [Pharo-dev] clarifying pharo crashing issue(s)

by stephan

On 27-11-17 12:08, Tudor Girba wrote: > How do they crash? When you run something specific? Different things. The script crashed reliably on all my machines the last time I checked. Stephan

Nov. 27, 2017

Re: [Pharo-dev] clarifying pharo crashing issue(s)

by Tudor Girba

Hi, How do they crash? When you run something specific? Doru > On Nov 27, 2017, at 11:56 AM, stephan <stephan(a)stack.nl> wrote: > > On 27-11-17 09:20, Tudor Girba wrote: >> Hi, >> There are recurrent reports that Pharo is crashing often. >> So, first question: >> - is Pharo crashing on another system than MacOS Sierra or HighSierra? > > Yes, older MacOS, Ubuntu 16.04LTS, Windows 7 & 10. Both 64 and 32 bit, > latest and stable vms. I'm mostly using PharoLauncher > > One of them is > > > |project| > Gofer it > smalltalkhubUser: 'StephanEggermont' project: 'MonticelloProjects'; > package: 'MonticelloProjects'; > load. > > project := (Smalltalk at: #MCProject) new location: > 'http://smalltalkhub.com/mc/StephanEggermont/Documentation/main'. > project read. > project saveToFile. > > Stephan > > -- www.tudorgirba.com www.feenk.com "Not knowing how to do something is not an argument for how it cannot be done."

Nov. 27, 2017

[Pharo 7.0-dev] Build #334: 20766-Increase-priority-of-FreeType-initialization

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

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…

Nov. 27, 2017

Re: [Pharo-dev] clarifying pharo crashing issue(s)

by stephan

On 27-11-17 09:20, Tudor Girba wrote: > Hi, > > There are recurrent reports that Pharo is crashing often. > So, first question: > - is Pharo crashing on another system than MacOS Sierra or HighSierra? Yes, older MacOS, Ubuntu 16.04LTS, Windows 7 & 10. Both 64 and 32 bit, latest and stable vms. I'm mostly using PharoLauncher One of them is |project| Gofer it smalltalkhubUser: 'StephanEggermont' project: 'MonticelloProjects'; package: 'MonticelloProjects'; load. project := (Smalltalk at: #MCProject) new location: 'http://smalltalkhub.com/mc/StephanEggermont/Documentation/main'. project read. project saveToFile. Stephan

Nov. 27, 2017

Re: [Pharo-dev] clarifying pharo crashing issue(s)

by Thierry Goubier

2017-11-27 9:38 GMT+01:00 Norbert Hartl <norbert(a)hartl.name>: > It is even crashing headless. I have one jenkins job where the build fails > everytime because the vm is crashing. 32 bit runs fine > Yes: my headless image building makefiles would segfault. Thierry > > Norbert > > Am 27.11.2017 um 09:34 schrieb Thierry Goubier <thierry.goubier(a)gmail.com > >: > > > > 2017-11-27 9:20 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > >> Hi, >> >> There are recurrent reports that Pharo is crashing often. >> >> However, at the moment I believe the reasons are not clarified. So, this >> mail is not about fixing the issues, but first about clarifying what they >> are. >> >> Namely: >> >> - I know about the typing problem on MacOS (Sierra or High Sierra). I >> encounter this problem daily (literally), and I know that I am not the only >> one. For example, this can occur when I type âclasssâ fast and then delete >> the last character. It is documented here: >> https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/141 >> >> - Some people talk about the FreeType problem, but I could not find a >> place where this is described. So, while this might be a problem, I am not >> sure that this problem is actually causing crashes. >> >> So, first question: >> - is Pharo crashing on another system than MacOS Sierra or HighSierra? >> > > Yes. > > On Linux (Ubuntu 16.04 / 17.04), 64bits Pharo segfaults if you use either > the stable or the latest vm from get.pharo.org. > > >> - how does the FreeType problem look like? >> > > ? It doesn't seems to be related. > > Regards, > > Thierry > > >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Beauty is where we see it." >> >> >> >> >> >> >

Nov. 27, 2017

[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

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…

Nov. 27, 2017