Moose-dev

moose-dev@list.inf.unibe.ch

6630 discussions

Re: [Pharo-dev] Re: Segmentation fault on Moose 6.1 Build

by Tudor Girba

Thanks. I have switched the Moose job back to using the latest image. Let’s see how it works. Cheers, Doru > On Mar 3, 2017, at 9:19 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Esteban created a working fix for this issue. > > Cheers, > -- Pavel > > 2017-03-03 3:16 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > To confirm specific reproducibility, using... > http://files.pharo.org/image/60/60421.zip > > I did... > $ cd opensmalltalk-vm > $ git checkout d54edc56 > $ git log > commit d54edc5638c9f90c80f214e59e19240f8ead87f8 > Author: Eliot Miranda <eliot.miranda(a)gmail.com> > Date: Thu Mar 2 09:53:05 2017 -0800 > CogVM source as per VMMaker.oscog-eem.2143 > Fix regression in Sista sources due to receiverTags work. > > $ cd build.linux32x86/pharo.cog.spur/build.debug > $ cd products/debug/phcogspurlinuxht > $ pharo ~/temp/Case19785/Pharo-60421.image > > World > Playground, evaluate... > surf := AthensCairoSurface extent: Display extent. > Display getCanvas drawImage: surf asForm at: 0@0 > > 70% ==> image seg fault > 30% ==> PrimitiveFailed: primitive #primSignal:andReturnAs:fromContext: > > but doing > Smalltalk snapshot: true andQuit: true. > surf := AthensCairoSurface extent: Display extent. > Display getCanvas drawImage: surf asForm at: 0@0. > > 100% ==> PrimitiveFailed: primitive #primSignal:andReturnAs:fromContext: > > > Evaluate the following in Playground for 100% segfault from command line. > > EllipseMorph compile: 'step > |surf| > [ surf := AthensCairoSurface extent: Display extent. > Display getCanvas drawImage: surf asForm at: 0@0. > ] on: Error do: [ ]. > self position: self position + (50@0). "To observe survival of seg fault" '. > Smalltalk snapshot: true andQuit: true. > EllipseMorph new openInWorld. > > > btw, I'm on 32-bit Debian 8 Jessie > $ uname -a > Linux dom0 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) i686 GNU/Linux > > cheers -ben > > > On Fri, Mar 3, 2017 at 12:08 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > Hi Eliot, > > > > > > > > Thanks to take care of this issue! > > > > > > > > Pavel opened a bug issue here: > > https://pharo.fogbugz.com/f/cases/19785/Athens-crashes-the-VM . You need the > > latest Pharo image and VM and it crashes under Linux (32-bit) and OSX (El > > Captain, 32-bit VM). And I personally tried with Windows7 and the bug > > happens too. > > > > > > > > To reproduce: Morph new testAthensRender > > > > > > > > An extract of the opened issue: > > > > > > > > Edited by Pavel Krivanek 02/03/2017 (Today) 16:10 > > > > An empty surface crashes it too: > > surf := AthensCairoSurface extent: Display extent. > > Display getCanvas drawImage: surf asForm at: 0@0 > > > > > > > > The problem is in the method AthensCairoSurface>>#asForm where the previous > > slice started to add 1 to surface heigth > > > > > > > > Well, I tried to revert AthensCairoSurface>>#asForm which fixes this > > particular case but Roassal still crashes on copyBits > > > > > > > > Cheers, > > > > Vincent > > > > > > > > De : Moose-dev [mailto:moose-dev-bounces@list.inf.unibe.ch] De la part de > > Eliot Miranda > > Envoyé : jeudi 2 mars 2017 17:03 > > À : Pharo Development List > > Cc : Moose-related development; Squeak Virtual Machine Development > > Discussion > > Objet : [Moose-dev] Re: [Pharo-dev] Segmentation fault on Moose 6.1 Build > > > > Hi Vincent, > > > > first, apologies for the inconvenience, second, thanks! I badly need > > reproducible failure cases to get the remaining bugs out of the compactor > > and you have just provided me with one. Can you send me the information I > > need to reproduce the build? What platforms does it fall on? > > > > On Thu, Mar 2, 2017 at 2:23 AM, Blondeau Vincent > > <vincent.blondeau(a)worldline.com> wrote: > > > > Hi, > > > > The latest builds of the Moose6.1 image are failing due to a segmentation > > fault. > > > > Here is the link to the last build: > > https://ci.inria.fr/moose/job/moose-6.1/550/console > > > > How can we fix this? > -- www.tudorgirba.com www.feenk.com "Beauty is where we see it."

7 years, 10 months

How to know when a playground was executed and storing the result?

by Offray Vladimir Luna Cárdenas

Hi, For the Grafoscopio notebook I would like to store the results of playground executions. That would imply to know when a playground was executed and which was the result[1]. We have been talking about that in the Pharo users mailing list and Ben and Phill are bringing some light on that, but I would like to invite Moose community to participate also. I have been looking at some inspector and playground blog posts, but the ones I have found are about creating custom views of objects you would like to extend, instead of capturing the output. [1] http://forum.world.st/How-to-capture-the-execution-of-a-playground-tt493627… There is any way to do that? Offray

7 years, 10 months

Google Summer of Code 2017: Call for mentors for Pharo Consortium

by Serge Stinckwich

Heartiest Congratulations ! Pharo Consortium has been selected as a mentor organisation for Google Summer of Code 2017. Google Summer of Code is a global program focused on introducing students to open source software development. Students work on a 3 month programming project with an open source organisation during their break from university. Read more at https://summerofcode.withgoogle.com/ How the program works ? Organizations: Open source projects apply to be mentor organizations. Once accepted, organizations discuss possible ideas with students and then decide on the proposals they wish to mentor for the summer. They provide mentors to help guide each student through the program. Mentors: Existing contributors with the organizations can choose to mentor a student project. Mentors and students work together to determine appropriate milestones and requirements for the summer. Mentor interaction is a vital part of the program. A mentor may propose or endorse a project and each project has to be about Pharo or its ecosystem (e.g., a library). Projects will be mentored by one or more mentors and executed by one student. Students: Students contact the mentor organizations they want to work with and write up a project proposal for the summer. If accepted, students spend a month integrating with their organizations prior to the start of coding. Students then have three months to code, meeting the deadlines agreed upon with their mentors. Student coding period: May 30 - Aug 29 (Entire timeline can be viewed at: https://summerofcode.withgoogle.com/how-it-works/#timeline). Student stipend: https://developers.google.com/open-source/gsoc/help/student-stipends We are currently at the phase of identifying mentors and projects. The next phases will be about students selecting projects, and the community selecting the projects with their associated mentors and students which will be sponsored by the GSOC program. How to register ? Simply by replying to this email and joining the Slack channel... to have more discussion about what project the mentor will take up, what she/he wants at the end of the coding period and then we can invite them to the GSoC org dashboard). Hence, we invite regular & enthusiastic Pharo contributors to be a mentor with Pharo Consortium for GSoC 2017: 1. Kindly respond on this thread if you'd like to be a mentor, or wish to propose a project. An existing list of projects is already available here: http://gsoc.pharo.org/ and we already have a handful of projects and mentors chosen. Feel free to collaborate with existing mentors as well. 2. Join dedicated channels, #gsoc-students for general interactions with students & #gsoc-planning channel only for GSOC admins and mentors on Pharo slack. In order to get an invitation for pharoproject.slack.com visit the URL here: http://slackinvites.pharo.org/ 3. Please open relevant issues and make a roadmap of the projects being mentored by you so that students can start contributing to them already. If you want to mentor a project and there is no open-source repository at the moment, please built one ASAP. 4. If you know any students that might be interested to work on Pharo during the summer and be a part of GSoC as well, please ask him/her to start contributing to the Pharo projects, discuss their proposal, follow instructions that shall be posted soon in this mailing thread and submit their application by April 3, 2017. We don't know the number of slots attributed by Google to Pharo org, but the more students proposal we will receive, the more slots will be attributed to us. We remind you about the mentor responsibilities: ... to your Org Admins - Communicate availability and interaction expectations - Inform when mentoring capacity will be reduced, as early as possible (e.g., family, health, vacation) - Inform when there is an issue with a student - Lacking communication, activity, visibility (MIA), or progress - Participant Agreement violations (e.g., plagiarism, harassment, fraud) - Bad fit or stepping down - Formally evaluate student participation. - Communicate with admin and student before failing ... to your Students - Help and/or teach the student - how to be a part of your community - communicate more effectively and in the open - work with your org’s preferred communication channel (IRC, Slack, etc) - use your org’s version control system - ask good questions and get answers to their questions - provide convincing technical argument and constructive discussion - be independently motivated and productive - solve difficult technical problems - Keep track of their progress, keep student informed as to their status - Communicate on a regular basis, once a week or better (for GSoC) - Give constructive feedback, be patient, and be respectful - Respond to questions within 24 hours (occasionally under 36 hours is ok) - Establish realistic work objectives and timeline expectations - Re-evaluate scope with student when significantly ahead of or behind expectations - Work with devs and community to facilitate acceptance of student work Read more about responsibilities here: https://developers.google.com/open-source/gsoc/help/responsibilities Looking forward to a great guided summer by the talented mentors of our organisation. Warm Regards Pharo Organisation Admins (Alexandre Bergel, Jigyasa Grover, Serge Stinckwich & Yuriy Tymchuk)

7 years, 10 months

roassal2 job

by Tudor Girba

Hi, Something seems to be wrong with the Roassal2 job: it does not end. Could someone take a look? https://ci.inria.fr/moose/job/roassal2/ Cheers, Doru -- www.tudorgirba.com www.feenk.com "We can create beautiful models in a vacuum. But, to get them effective we have to deal with the inconvenience of reality."

7 years, 10 months

[Moose-dev] Student of Stéphane Ducasse: Roassal project

by said yebbah

Hello, We‘re a group of 3 students from a course with Stéphane Ducasse in university of Lille 1, and we’re beginners in Pharo and for the next 2 weeks we have to work on an open source project. we choose Roassal project. So we would like to know what's the prupose of ideas that we've to do ? In fact, in the moments we're at the point of discovering Roassal. Thanks,

7 years, 10 months

Re: Student of Stéphane Ducasse: Roassal project

by Serge Stinckwich

This is better to answer on the mailing-list. Regards, On Fri, Mar 3, 2017 at 3:30 PM, said yebbah <said.yebbah(a)hotmail.com> wrote: > Bonjour, > > > First we thank you in advance for your reply, it seems an interesting > suggestion project, we'll try to start doing the same thing with Roassel > but for the moment we're beginners and we have only 2 weeks, we wish that > you help us for the next time. > > > this's list email of other memebers group: > > hamid.lafredi(a)etudiant.univ-lille1.fr > > martin.bigand(a)etudiant.univ-lille1.fr > > > > > > > On Fri, Mar 3, 2017 at 2:34 PM, said yebbah <said.yebbah(a)hotmail.com> > wrote: > > Hello, > > Bonjour, > > > We‘re a group of 3 students from a course with Stéphane Ducasse in > > university of Lille 1, > > and we’re beginners in Pharo and for the next 2 weeks we have to work on > an > > open source project. > > we choose Roassal project. So we would like to know what's the prupose of > > ideas that we've to do ? > > In fact, in the moments we're at the point of discovering Roassal. > > Welcome in the community ! > > I have one idea for a small project for students. > I give this link to my students for a lecture at Paris 6 University, > is it possible to do the same with Roassal: > https://github.com/SergeStinckwich/ARE-UPMC/blob/ > master/ARE-DYNAMIC/fiche3.ipynb > and if not how you fix that ? > > Thank you. > > -- > Serge Stinckwich > UCN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > Serge Stinckwich - Home | #DNU <http://www.doesnotunderstand.org/> > www.doesnotunderstand.org > Welcome to #DNU! #DNU is the home page of Serge Stinckwich, full-time > computer scientist and part-time Smalltalk evangelist. Important We are > currently conducting a ... > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > Moose-dev Info Page - unibe.ch > <https://www.list.inf.unibe.ch/listinfo/moose-dev> > www.list.inf.unibe.ch > To see the collection of prior postings to the list, visit the Moose-dev > Archives. Using Moose-dev: To post a message to all the list members, send > ... > > > -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

7 years, 10 months

Different versions of Moose 6.0

by Serge Stinckwich

Dear all, apparently Moose 6.0 version available on the website: http://www.moosetechnology.com/ is not the same version used on SmalltalkCI. 1st one is : Pharo5.0 Latest update: #50761 and the other one: Pharo5.0 Latest update: #50770 Is it possible to have same version on both sides ? :-) Because we have some code that only fails on the CI and this source of confusion. Regards, -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

7 years, 10 months

Re: [Pharo-dev] Growing large images: the case of Moose models

by Blondeau Vincent

Thanks Eliot for the implementation of the new compactor! Just to add a piece of information: the mse imported have a size of 40Mb. Cheers, Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Clément Bera Envoyé : vendredi 3 mars 2017 11:56 À : Discusses Development of Pharo Objet : [Pharo-dev] Growing large images: the case of Moose models Hello everyone, This morning I investigated with Vincent Blondeau a problem reported by the Moose community a while ago: loading Moose model is slower in Spur (Pharo 5+) than in pre-Spur (Pharo 4 and older). In general, this problem was present for anyone growing images to a significant size. To investigate the problem, we loaded a 200Mb[3] Moose model on a 250Mb image, growing the image to 450Mb. Loading such a model takes 2 minutes in Spur and 1m30s in pre-Spur VMs. Using the stable Pharo VM, the analysis results were the following: - total time spent to load the Model: 2 minutes - time spent in full GC: 1 minute (4 fullGCs) - time spent in scavenges[1]: 15 seconds On the 2 minutes spent, we have 50% of the time spent in full GCs, 12.5% in scavenges, 37.5% executing code. We then used the latest VM that features the new compactor (VM from beginning of March 2017 and over). The full GC execution time went down from 1 minute to 2 seconds. In addition, we increased the size of Eden[2] from 4Mb to 12Mb. Time spent in scavenges decreased from 15 seconds to 5 seconds. Overall, loading the model is now taking ~50 seconds instead of 2 minutes. To increase Eden size, one needs to run a script similar to: | currentEdenSize desiredEdenSize | currentEdenSize := Smalltalk vm parameterAt: 44. desiredEdenSize := currentEdenSize * 4. Smalltalk vm parameterAt: 45 put: desiredEdenSize. And then restart the image. I hope this report can be useful for some of you. I will try to make a blog post out of it, detailing other GC settings one can change from the image to improve performance. Best, Clement [1] A scavenge is basically the garbage collection of only young objects [2] Eden is basically the space where objects are initially allocated. [3] All numbers in the report are order of magnitudes and not precise numbers !!!************************************************************************************* "Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

7 years, 10 months

Segmentation fault on Moose 6.1 Build

by Blondeau Vincent

Hi, The latest builds of the Moose6.1 image are failing due to a segmentation fault. Here is the link to the last build: https://ci.inria.fr/moose/job/moose-6.1/550/console How can we fix this? Thanks in advance, Cheers, Vincent !!!************************************************************************************* "Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

7 years, 10 months

Re: [Pharo-dev] Re: Segmentation fault on Moose 6.1 Build

by Tudor Girba

Hmm, it looks like something changed and the build is now yellow. Does anyone have the time to check this mysterious behavior? Cheers, Doru > On Mar 2, 2017, at 1:24 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > I will try to make some easier way to reproduce it and open an issue > > -- Pavel > > 2017-03-02 11:58 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > Hm, I haven't check the time of the failing build... Yes, it will be related... > > 2017-03-02 11:51 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > Except for tiny changes in Athens in 60419 :) > > Doru > > > > On Mar 2, 2017, at 11:33 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > > > On image side nothing relevant happened in 60418 where it started to fail. > > > > -- Pavel > > > > 2017-03-02 11:31 GMT+01:00 Blondeau Vincent <vincent.blondeau(a)worldline.com>: > > I heard that the gc compactor have changed. > > > > Cheers, > > Vincent > > > > > -----Message d'origine----- > > > De : Moose-dev [mailto:moose-dev-bounces@list.inf.unibe.ch] De la part de > > > Tudor Girba > > > Envoyé : jeudi 2 mars 2017 11:29 > > > À : Pharo Development List > > > Cc : Moose-related development > > > Objet : [Moose-dev] Re: [Pharo-dev] Segmentation fault on Moose 6.1 Build > > > > > > Hi, > > > > > > Was there a change related to the stable VM? > > > > > > Cheers, > > > Doru > > > > > > > > > > On Mar 2, 2017, at 11:23 AM, Blondeau Vincent > > > <vincent.blondeau(a)worldline.com> wrote: > > > > > > > > Hi, > > > > > > > > The latest builds of the Moose6.1 image are failing due to a segmentation > > > fault. > > > > Here is the link to the last build: > > > > https://ci.inria.fr/moose/job/moose-6.1/550/console > > > > > > > > How can we fix this? > > > > > > > > Thanks in advance, > > > > > > > > Cheers, > > > > Vincent > > > > > > > > > > > > > > > !!!******************************************************** > > > *********** > > > > ****************** "Ce message et les pièces jointes sont > > > > confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut > > > également être protégé par le secret professionnel. Si vous recevez ce > > > message par erreur, merci d'en avertir immédiatement l'expéditeur et de le > > > détruire. L'intégrité du message ne pouvant être assurée sur Internet, la > > > responsabilité de Worldline ne pourra être recherchée quant au contenu de > > > ce message. Bien que les meilleurs efforts soient faits pour maintenir cette > > > transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à > > > cet égard et sa responsabilité ne saurait être recherchée pour tout dommage > > > résultant d'un virus transmis. > > > > > > > > This e-mail and the documents attached are confidential and intended > > > solely for the addressee; it may also be privileged. If you receive this e-mail in > > > error, please notify the sender immediately and destroy it. As its integrity > > > cannot be secured on the Internet, the Worldline liability cannot be triggered > > > for the message content. Although the sender endeavours to maintain a > > > computer virus-free network, the sender does not warrant that this > > > transmission is virus-free and will not be liable for any damages resulting > > > from any virus transmitted.!!!" > > > > <dump.txt> > > > > > > -- > > > www.tudorgirba.com > > > www.feenk.com > > > > > > “Live like you mean it." > > > > > > _______________________________________________ > > > Moose-dev mailing list > > > Moose-dev(a)list.inf.unibe.ch > > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > > > !!!************************************************************************************* > > "Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. > > > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!" > > > > -- > www.tudorgirba.com > www.feenk.com > > "Yesterday is a fact. > Tomorrow is a possibility. > Today is a challenge." > > > > > > > -- www.tudorgirba.com www.feenk.com "Beauty is where we see it."

7 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev