February 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [regression reporter]regression occurred

by Sven Van Caekenberghe

> On 24 Feb 2016, at 11:09, Max Leske <maxleske(a)gmail.com> wrote: > > Hereâs an idea: > > 1. exclude Zinc tests from the validation tests > 2. after the build, trigger a Travis build on Github via API (I just set that up for Fuel, so I can provide help there) > 3. the Travis build only runs the Zinc tests > 4. read build results from Travis > > Very ugly, I know. But itâs done rather quickly and should solve all the network problems. I don't think the current problem is severe enough to put much work in it, right now. But would it not be much better to run everything (all tests) on Travis ? At first, maybe just as a limited experiment ? I would love to see that. > Max > >> On 24 Feb 2016, at 11:01, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> The problem is that managing a CI server for a project like Pharo would be >> one full time engineer in a company, we do not have the manpower. >> >> So we need to find solutions that are cheap to do. >> >>> On 24 Feb 2016, at 10:50, Ben Coman <btc(a)openinworld.com> wrote: >>> >>> Maybe there can be a pre-test run at the shell level to flag that the >>> required network connectivity is available to run that test inside the >>> image. Pharo startup could read them in while starting. >>> cheers -ben >>> >>> On Wed, Feb 24, 2016 at 5:38 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>>> one idea could be to add this to the filter of the CI runner. >>>> >>>> It seems it fails due to network setup problems that are specific to the CI server... >>>> >>>>> On 24 Feb 2016, at 09:07, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>> >>>>> The following test seems to be failing a lot lately on the CI infrastructure, yet it always succeeds for me on my machine. Is there anybody who sees this fail on their machines ? >>>>> >>>>>> On 24 Feb 2016, at 08:36, no-reply(a)ci.inria.fr wrote: >>>>>> >>>>>> https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/labe… >>>>>> >>>>>> 1 regressions found. >>>>>> Zinc.Zodiac.ZnHTTPSTests.testAmazonAWS >>>>> >>>>> >>>> >>>> >>> >> >> > >

Feb. 24, 2016

Re: [Pharo-dev] [Pharo-users] [Moose-dev] Re: Call for action for Roassal

by Peter UhnÃ¡k

On Wed, Feb 24, 2016 at 11:03 AM, Martin BÃ¤hr < mbaehr(a)email.archlab.tuwien.ac.at> wrote: > Excerpts from Peter UhnÃ¡k's message of 2016-02-24 10:35:05 +0100: > > In any case, I wrote a simpler layout delegator in Roassal that delegates > > the layouting to graphviz and it works reasonably well, so I could > probably > > add it to Roassal (you however need graphviz installed and it would add > > another dependency to Roassal, which I'm not so keen on). > > how does that work? does it ask graphviz for the position of the nodes and > then > recreate that in roassal? > Yes, I generate .dot file that describes the nodes I want the layout for (that includes the dimensions of it), and then the .dot file is passed to GraphVizâ¦ from there I parse the generated SVG file (they can also output other formats like txt, or xml) and move the Roassal nodes. > > > Maybe also OGDF (http://ogdf.net/doku.php) could be used if you are ok > with > > GPLâ¦ they have their own graph format so there could be some interaction. > > this would work the same as with graphviz as an additional dependency on > ogdf, right? > GraphViz is good enough for generic graphs, but OGDF is well-founded and much more powerful layouting library. However C++ coding is required if one wants to use it. Peter

Feb. 24, 2016

Re: [Pharo-dev] [regression reporter]regression occurred

by Max Leske

Hereâs an idea: 1. exclude Zinc tests from the validation tests 2. after the build, trigger a Travis build on Github via API (I just set that up for Fuel, so I can provide help there) 3. the Travis build only runs the Zinc tests 4. read build results from Travis Very ugly, I know. But itâs done rather quickly and should solve all the network problems. Max > On 24 Feb 2016, at 11:01, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > The problem is that managing a CI server for a project like Pharo would be > one full time engineer in a company, we do not have the manpower. > > So we need to find solutions that are cheap to do. > >> On 24 Feb 2016, at 10:50, Ben Coman <btc(a)openinworld.com> wrote: >> >> Maybe there can be a pre-test run at the shell level to flag that the >> required network connectivity is available to run that test inside the >> image. Pharo startup could read them in while starting. >> cheers -ben >> >> On Wed, Feb 24, 2016 at 5:38 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> one idea could be to add this to the filter of the CI runner. >>> >>> It seems it fails due to network setup problems that are specific to the CI server... >>> >>>> On 24 Feb 2016, at 09:07, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> The following test seems to be failing a lot lately on the CI infrastructure, yet it always succeeds for me on my machine. Is there anybody who sees this fail on their machines ? >>>> >>>>> On 24 Feb 2016, at 08:36, no-reply(a)ci.inria.fr wrote: >>>>> >>>>> https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/labe… >>>>> >>>>> 1 regressions found. >>>>> Zinc.Zodiac.ZnHTTPSTests.testAmazonAWS >>>> >>>> >>> >>> >> > >

Feb. 24, 2016

Re: [Pharo-dev] [Bloc] MDLColor and new gradient

by Guillaume Larcheveque

You can try it with: Metacello new smalltalkhubUser: 'KevinLanvin' project: 'MaterialDesignLite'; configuration: 'MaterialDesignLite'; version: #development; load: #(#colors) 2016-02-23 9:13 GMT+01:00 stepharo <stepharo(a)free.fr>: > Hi > > Guillaume Larcheveque in Telescope added support for MDLColor > http://www.materialui.co/colors > > and nice gradient building. > > I asked him if we could extract this functionality and move it into Pharo > because > it will be usefull for Pharo, Bloc, and Roassal. > > A first step could be to have MDLColor subclass as it is now > but the second step would be to rethink Color and palette. > > May be we should have some Palette > > And we could have (brainstorming) > > (ColorBuilder from: MDLPalette) > -> aColorBuilder > aColorBuilder red > -> .... > > Stef > > > -- *Guillaume Larcheveque*

Feb. 24, 2016

[pharo-project/pharo-core] 9d9b04: 50606

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 9d9b040d8c8f350adaddfa76e695fb04908b7442 https://github.com/pharo-project/pharo-core/commit/9d9b040d8c8f350adaddfa76… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-02-24 (Wed, 24 Feb 2016) Changed paths: A ConfigurationOfSton.package/ConfigurationOfSton.class/class/accessing/catalogContactInfo.st A ConfigurationOfSton.package/ConfigurationOfSton.class/class/accessing/catalogDescription.st A ConfigurationOfSton.package/ConfigurationOfSton.class/class/accessing/catalogKeywords.st M ConfigurationOfSton.package/ConfigurationOfSton.class/instance/symbolic versions/stable_.st A ConfigurationOfSton.package/ConfigurationOfSton.class/instance/versions/version15_.st A ConfigurationOfSton.package/ConfigurationOfSton.class/instance/versions/version16_.st A ConfigurationOfSton.package/ConfigurationOfSton.class/instance/versions/version17_.st A STON-Core.package/STON.class/class/accessing/associationClass.st A STON-Core.package/STON.class/class/convencience/fromStreamWithComments_.st A STON-Core.package/STON.class/class/convencience/fromStringWithComments_.st A STON-Core.package/STONCStyleCommentsSkipStream.class/README.md A STON-Core.package/STONCStyleCommentsSkipStream.class/class/instance creation/on_.st A STON-Core.package/STONCStyleCommentsSkipStream.class/definition.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/collectionSpecies.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/next.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/nextLine.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/next_.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/next_into_.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/next_into_startingAt_.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/peek.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/peekFor_.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/position.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/readInto_startingAt_count_.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/skip_.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/upToEnd.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/upTo_.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/wrappedStream.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/initialize-release/close.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/initialize-release/on_.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/private/consumeComment.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/private/consumeToCommentEnd.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/private/consumeToEOL.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/private/escape.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/private/handleStringDelimiter_.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/private/insideString.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/private/nextNonCommentChar.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/testing/atEnd.st A STON-Core.package/STONCStyleCommentsSkipStream.class/instance/testing/isBinary.st M STON-Core.package/STONReader.class/instance/parsing/parseValue.st M STON-Core.package/STONWriter.class/class/class initialization/initializeSTONCharacters.st M STON-Core.package/STONWriter.class/definition.st A STON-Core.package/STONWriter.class/instance/initialize-release/asciiOnly_.st M STON-Core.package/STONWriter.class/instance/initialize-release/initialize.st M STON-Core.package/STONWriter.class/instance/private/encodeCharacter_.st M STON-Core.package/extension/Association/instance/stonOn_.st A STON-Core.package/extension/Class/class/fromSton_.st A STON-Core.package/extension/Class/instance/stonOn_.st A STON-Core.package/extension/ClassDescription/instance/stonContainSubObjects.st A STON-Core.package/extension/Metaclass/class/fromSton_.st A STON-Core.package/extension/TApplyingOnClassSide/instance/stonName.st A STON-Core.package/extension/TApplyingOnClassSide/instance/stonOn_.st A STON-Tests.package/STONCStyleCommentsSkipStreamTests.class/README.md A STON-Tests.package/STONCStyleCommentsSkipStreamTests.class/definition.st A STON-Tests.package/STONCStyleCommentsSkipStreamTests.class/instance/testing/testCommentInString.st A STON-Tests.package/STONCStyleCommentsSkipStreamTests.class/instance/testing/testMultiLineComment.st A STON-Tests.package/STONCStyleCommentsSkipStreamTests.class/instance/testing/testNonComment.st A STON-Tests.package/STONCStyleCommentsSkipStreamTests.class/instance/testing/testSTON.st A STON-Tests.package/STONCStyleCommentsSkipStreamTests.class/instance/testing/testSingleLineComment.st M STON-Tests.package/STONLargeWriteReadTests.class/instance/private/serialize_.st A STON-Tests.package/STONReaderTests.class/instance/tests/testClass.st A STON-Tests.package/STONReaderTests.class/instance/tests/testMetaclass.st A STON-Tests.package/STONTestAssociation.class/README.md A STON-Tests.package/STONTestAssociation.class/definition.st A STON-Tests.package/STONTestAssociation.class/instance/accessing/key_value_.st A STON-Tests.package/STONTestAssociation.class/instance/accessing/now.st A STON-Tests.package/STONTestAssociation.class/instance/accessing/timestamp.st A STON-Tests.package/STONTestAssociation.class/instance/accessing/value_.st A STON-Tests.package/STONTests.class/instance/tests/testFromStringWithComments.st A STON-Tests.package/STONWriteReadCommentsTests.class/README.md A STON-Tests.package/STONWriteReadCommentsTests.class/definition.st A STON-Tests.package/STONWriteReadCommentsTests.class/instance/private/materialize_.st A STON-Tests.package/STONWriteReadCommentsTests.class/instance/private/serialize_.st A STON-Tests.package/STONWriteReadTests.class/instance/tests/testClasses.st A STON-Tests.package/STONWriteReadTests.class/instance/tests/testCustomAssociations.st A STON-Tests.package/STONWriterTests.class/instance/private/serializeAsciiOnly_.st A STON-Tests.package/STONWriterTests.class/instance/tests/testClass.st M STON-Tests.package/STONWriterTests.class/instance/tests/testDoubleQuotedString.st A STON-Tests.package/STONWriterTests.class/instance/tests/testMetaclass.st M STON-Tests.package/STONWriterTests.class/instance/tests/testString.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50605.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50606.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50605.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50606.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Settings.package/SettingsStonWriter.class/instance/actions/store.st Log Message: ----------- 50606 16893 Update STON https://pharo.fogbugz.com/f/cases/16893 http://files.pharo.org/image/50/50606.zip

Feb. 24, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50606 Home: https://github.com/pharo-project/pharo-core

Feb. 24, 2016

Re: [Pharo-dev] [regression reporter]regression occurred

by Marcus Denker

The problem is that managing a CI server for a project like Pharo would be one full time engineer in a company, we do not have the manpower. So we need to find solutions that are cheap to do. > On 24 Feb 2016, at 10:50, Ben Coman <btc(a)openinworld.com> wrote: > > Maybe there can be a pre-test run at the shell level to flag that the > required network connectivity is available to run that test inside the > image. Pharo startup could read them in while starting. > cheers -ben > > On Wed, Feb 24, 2016 at 5:38 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> one idea could be to add this to the filter of the CI runner. >> >> It seems it fails due to network setup problems that are specific to the CI server... >> >>> On 24 Feb 2016, at 09:07, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> The following test seems to be failing a lot lately on the CI infrastructure, yet it always succeeds for me on my machine. Is there anybody who sees this fail on their machines ? >>> >>>> On 24 Feb 2016, at 08:36, no-reply(a)ci.inria.fr wrote: >>>> >>>> https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/labe… >>>> >>>> 1 regressions found. >>>> Zinc.Zodiac.ZnHTTPSTests.testAmazonAWS >>> >>> >> >> >

Feb. 24, 2016

Re: [Pharo-dev] [regression reporter]regression occurred

by Sven Van Caekenberghe

> On 24 Feb 2016, at 10:50, Ben Coman <btc(a)openinworld.com> wrote: > > Maybe there can be a pre-test run at the shell level to flag that the > required network connectivity is available to run that test inside the > image. Pharo startup could read them in while starting. These networking problems are issues specific to the CI infrastructure. But these are real bugs: we don't know why they happen, we have no idea. It is not that there is no network, else almost everything would fail immediately. It should not be too much asked in the 21st century for a server to be able to access any website, right ? > cheers -ben > > On Wed, Feb 24, 2016 at 5:38 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> one idea could be to add this to the filter of the CI runner. >> >> It seems it fails due to network setup problems that are specific to the CI server... >> >>> On 24 Feb 2016, at 09:07, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> The following test seems to be failing a lot lately on the CI infrastructure, yet it always succeeds for me on my machine. Is there anybody who sees this fail on their machines ? >>> >>>> On 24 Feb 2016, at 08:36, no-reply(a)ci.inria.fr wrote: >>>> >>>> https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/labe… >>>> >>>> 1 regressions found. >>>> Zinc.Zodiac.ZnHTTPSTests.testAmazonAWS >>> >>> >> >> >

Feb. 24, 2016

Re: [Pharo-dev] [regression reporter]regression occurred

by Ben Coman

Maybe there can be a pre-test run at the shell level to flag that the required network connectivity is available to run that test inside the image. Pharo startup could read them in while starting. cheers -ben On Wed, Feb 24, 2016 at 5:38 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > one idea could be to add this to the filter of the CI runner. > > It seems it fails due to network setup problems that are specific to the CI server... > >> On 24 Feb 2016, at 09:07, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> The following test seems to be failing a lot lately on the CI infrastructure, yet it always succeeds for me on my machine. Is there anybody who sees this fail on their machines ? >> >>> On 24 Feb 2016, at 08:36, no-reply(a)ci.inria.fr wrote: >>> >>> https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/labe… >>> >>> 1 regressions found. >>> Zinc.Zodiac.ZnHTTPSTests.testAmazonAWS >> >> > >

Feb. 24, 2016

Re: [Pharo-dev] [Moose-dev] Call for action for Roassal

by Anne Etien

> Le 24 fÃ©vr. 2016 Ã 10:35, Peter UhnÃ¡k <i.uhnak(a)gmail.com> a Ã©crit : > > > > On Wed, Feb 24, 2016 at 10:28 AM, Anne Etien <anne.etien(a)univ-lille1.fr <mailto:anne.etien@univ-lille1.fr>> wrote: > Hi Alexandre, > > In a wonderful world, I would like: > - a real graph layout (like in graphviz) that can take into account around hundred nodes and several hundred of edges and place the nodes in order to see something. Currently, I have to use the circle layout and it looks strange. > > Unfortunately making real graph layouts is really hard issueâ¦ I've wrote my bachelor thesis about this and didn't get very far; it's bit of a nightmare if you don't have good foundations. :â( I know. I tried but my mathematical background and my time were not enough. I got the research paper explaining the algorithm of Graphviz but even with that, it was very complex. However, since some tools (as graphviz) do it, we should have it. Anne > > In any case, I wrote a simpler layout delegator in Roassal that delegates the layouting to graphviz and it works reasonably well, so I could probably add it to Roassal (you however need graphviz installed and it would add another dependency to Roassal, which I'm not so keen on). > > Maybe also OGDF (http://ogdf.net/doku.php <http://ogdf.net/doku.php>) could be used if you are ok with GPLâ¦ they have their own graph format so there could be some interaction. > > Peter > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

Feb. 24, 2016