July 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] NeoCSV doc is now on Gutenberg :)

by Sean P. DeNigris

StÃ©phane Ducasse wrote > I love reading documentation :) Yes, and the NeoCSV doc is really good :) It felt like having an expert mentor me... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-dev-NeoCSV-doc-is-now-on-Gutenberg-tp4697733p46… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 8, 2013

Re: [Pharo-dev] filetree jenkins job

by Camillo Bruni

On 2013-07-08, at 01:59, Dale K. Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > Cami, > > Even worse, I don't get _any_ information about failures. When I run unit tests headless I get the following in my output: > > =============================================================================== > Notice: Errors in script loaded from /home/travis/dalehenrich-builderCI-3062fdf/builds/travisCI/travisCI.st > =============================================================================== > > No stacks in the debug log, so I am completely blind when I run Pharo3.0 builds ... been happening about 2 weeks ... I assume there was a radical change to the way the Pharo3.0 reports headless errors, either by accident or on purpose... that's usually not a bug, it currently is a side-effect of Opal giving proper feedback about undefined variables. With the new classbuilder introduce we might have some side-effects as well (there is a reported case that Martin and Christophe found). > Christophe will be checking into this and I am sure he'll et me running again ... > > Until I can see what's happening with the builds I can't get the last little bits fixed for Pharo3.0 ... very close though:) sometimes what helps is running in jenkins mode, failing tests produce a serialized stack which can be drag n dropped onto an image for easier debugging. I use that on a regular basis when figuring out non-deterministic tests :) You can see such files here: https://ci.inria.fr/pharo-contribution/job/FileTree/PHARO=30,VERSION=stable…

July 8, 2013

Re: [Pharo-dev] filetree jenkins job

by Dale K. Henrichs

Cami, Even worse, I don't get _any_ information about failures. When I run unit tests headless I get the following in my output: =============================================================================== Notice: Errors in script loaded from /home/travis/dalehenrich-builderCI-3062fdf/builds/travisCI/travisCI.st =============================================================================== =============================================================================== Notice: Errors in script loaded from /home/travis/dalehenrich-builderCI-3062fdf/builds/travisCI/travisCI.st =============================================================================== =============================================================================== Notice: Errors in script loaded from /home/travis/dalehenrich-builderCI-3062fdf/builds/travisCI/travisCI.st =============================================================================== =============================================================================== Notice: Errors in script loaded from /home/travis/dalehenrich-builderCI-3062fdf/builds/travisCI/travisCI.st =============================================================================== =============================================================================== Notice: Errors in script loaded from /home/travis/dalehenrich-builderCI-3062fdf/builds/travisCI/travisCI.st =============================================================================== =============================================================================== Notice: Errors in script loaded from /home/travis/dalehenrich-builderCI-3062fdf/builds/travisCI/travisCI.st =============================================================================== No stacks in the debug log, so I am completely blind when I run Pharo3.0 builds ... been happening about 2 weeks ... I assume there was a radical change to the way the Pharo3.0 reports headless errors, either by accident or on purpose... Christophe will be checking into this and I am sure he'll et me running again ... Until I can see what's happening with the builds I can't get the last little bits fixed for Pharo3.0 ... very close though:) Dale ----- Original Message ----- | From: "Camillo Bruni" <camillobruni(a)gmail.com> | To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> | Sent: Sunday, July 7, 2013 3:11:38 PM | Subject: Re: [Pharo-dev] filetree jenkins job | | I will change SUnit first produce proper error messages for the | #shouldnt:raise: methods since I cannot properly debug them. | Additionally at the point where the #:assert: happens the wrong | exception is not in the context which means it does not get properly | serialized by our test framework. All in all, with a little effort | we could debug much easier. | | BTW: There are so many strange methods on TAssertable that I do not | understand | - #shouldFix: | - #executeShould:inScopeOf: | | and some that I honestly think they hurt more than they help: | - #shouldnt:raise:whoseDescriptionIncludes:description: and friends? | | On 2013-07-07, at 23:47, "Dale K. Henrichs" | <dale.henrichs(a)gemtalksystems.com> wrote: | | > Cami, | > | > I've been having trouble with getting any useful information from | > Pharo3.0 failures on travis-ci[1] for a week or so now ... | > Christophe will be looking into this for me... | > | > Dale | > | > [1] | > https://github.com/dalehenrich/filetree/issues/80#issuecomment-20162125 | > ----- Original Message ----- | > | From: "Camillo Bruni" <camillobruni(a)gmail.com> | > | To: pharo-dev(a)lists.pharo.org | > | Sent: Sunday, July 7, 2013 2:00:10 PM | > | Subject: [Pharo-dev] filetree jenkins job | > | | > | after I tried to get filetree with the tests installed and I | > | didn't | > | get it | > | the first time I decided to create a jenkins job. | > | | > | https://ci.inria.fr/pharo-contribution/job/FileTree/ | > | | > | | > | | |

July 7, 2013

Re: [Pharo-dev] filetree jenkins job

by Camillo Bruni

I will change SUnit first produce proper error messages for the #shouldnt:raise: methods since I cannot properly debug them. Additionally at the point where the #:assert: happens the wrong exception is not in the context which means it does not get properly serialized by our test framework. All in all, with a little effort we could debug much easier. BTW: There are so many strange methods on TAssertable that I do not understand - #shouldFix: - #executeShould:inScopeOf: and some that I honestly think they hurt more than they help: - #shouldnt:raise:whoseDescriptionIncludes:description: and friends? On 2013-07-07, at 23:47, "Dale K. Henrichs" <dale.henrichs(a)gemtalksystems.com> wrote: > Cami, > > I've been having trouble with getting any useful information from Pharo3.0 failures on travis-ci[1] for a week or so now ... Christophe will be looking into this for me... > > Dale > > [1] https://github.com/dalehenrich/filetree/issues/80#issuecomment-20162125 > ----- Original Message ----- > | From: "Camillo Bruni" <camillobruni(a)gmail.com> > | To: pharo-dev(a)lists.pharo.org > | Sent: Sunday, July 7, 2013 2:00:10 PM > | Subject: [Pharo-dev] filetree jenkins job > | > | after I tried to get filetree with the tests installed and I didn't > | get it > | the first time I decided to create a jenkins job. > | > | https://ci.inria.fr/pharo-contribution/job/FileTree/ > | > | >

July 7, 2013

Re: [Pharo-dev] filetree jenkins job

by Dale K. Henrichs

Cami, I've been having trouble with getting any useful information from Pharo3.0 failures on travis-ci[1] for a week or so now ... Christophe will be looking into this for me... Dale [1] https://github.com/dalehenrich/filetree/issues/80#issuecomment-20162125 ----- Original Message ----- | From: "Camillo Bruni" <camillobruni(a)gmail.com> | To: pharo-dev(a)lists.pharo.org | Sent: Sunday, July 7, 2013 2:00:10 PM | Subject: [Pharo-dev] filetree jenkins job | | after I tried to get filetree with the tests installed and I didn't | get it | the first time I decided to create a jenkins job. | | https://ci.inria.fr/pharo-contribution/job/FileTree/ | |

July 7, 2013

Re: [Pharo-dev] filetree jenkins job

by Benjamin

Cool :) Ben On Jul 7, 2013, at 11:00 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > after I tried to get filetree with the tests installed and I didn't get it > the first time I decided to create a jenkins job. > > https://ci.inria.fr/pharo-contribution/job/FileTree/ >

July 7, 2013

filetree jenkins job

by Camillo Bruni

after I tried to get filetree with the tests installed and I didn't get it the first time I decided to create a jenkins job. https://ci.inria.fr/pharo-contribution/job/FileTree/

July 7, 2013

Re: [Pharo-dev] NeoCSV doc is now on Gutenberg :)

by Sven Van Caekenberghe

Thanks, again ! On 07 Jul 2013, at 21:49, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi sven > > I converted and modified the documentation you did. I love reading documentation :) > This is still draft because some examples are missing but we have a solid basis. > > Stef > > <NeoCVS.pier.pdf>

July 7, 2013

YAML Parser?

by Stefan Marr

Hi: Is anyone aware of a YAML parser that's compatible with Pharo 1.4 and 2.0? (http://yaml.org/) I am using only the most basic features, so, it wouldn't need to be feature complete. Thanks Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

July 7, 2013

NeoCSV doc is now on Gutenberg :)

by StÃ©phane Ducasse

Hi sven I converted and modified the documentation you did. I love reading documentation :) This is still draft because some examples are missing but we have a solid basis. Stef

July 7, 2013