- Pharo-dev - lists.pharo.org

Re: [Pharo-project] LAst Phato core, Zn and proxy [WAS] Re: 1.3-Core

by Sven Van Caekenberghe

Hi Mariano, On 16 May 2011, at 09:36, Mariano Martinez Peck wrote: > Hi. I didn't follow the long thread, but in latest PharoCore (when Zn is present) I cannot use monticello because I cannot get out. > I am behind a proxy but with the previous network library it worked out of the box. > > Is this the same problem of Alexandre? is there an issue in the bugtracket? can we integrated? > is there a workarround so that I can continue using my image? This should all be fixed, in the latest Zn, which should be integrated soon, but that I cannot do. You can always just load Zn from its official repository over what Core has. Sven

May 16, 2011

Re: [Pharo-project] Amazon AWS S3 Monticello Mirror

by Sven Van Caekenberghe

On 16 May 2011, at 09:25, Marcus Denker wrote: > Yes! We should get that setup... very nice! > > Whose Amazon Account do we use? Currently, the demo is on my AWS account (part of http://zn.stfx.eu) To set this up properly, I need an AWS account held by some official body. This requires a credit card. There will be costs for storage on S3, network transfers and some small (micro) EC2 instance running the syncing bot. Let's say we store 10GB, transfer 10GB each month, run 1 micro instance continuously, that would be close to $25 each month, $300 a year. Doubling to 20GB would add like $5 a month. A new AWS account gets 1 year of a micro instance and some storage/transfer for free, so the first year would be less. Maybe we should discuss this further off list. Sven

May 16, 2011

Re: [Pharo-project] [TODO] 1.3

by Mariano Martinez Peck

On Mon, May 16, 2011 at 9:15 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > Core > ==== > > Open Issues: 20 > http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3 > Failing Tests: 1 > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/lastCompleted… > > Full > === > Open Issues: 8 > > http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3-DevImage > Failing Tests: 3 > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/lastCompletedBuild/t… > > I've removed XMLSupport so there are 2 less failing tests. > > => Most important next Issue to tackle: Get all tests green. > > It would be nice to get both Core and Full green. Than the idea is that in > the spirit of Continuous > Delivery, we just keep it green. No degeneration of trivial problems > (undeclards), fast roll-back of > problematic changes... > > The idea is to keep it in a state that we could, at a minumum, always say > "We could release next Friday". > And the best would be: "We could release today". > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > -- Mariano http://marianopeck.wordpress.com

May 16, 2011

[Pharo-project] LAst Phato core, Zn and proxy [WAS] Re: 1.3-Core

by Mariano Martinez Peck

Hi. I didn't follow the long thread, but in latest PharoCore (when Zn is present) I cannot use monticello because I cannot get out. I am behind a proxy but with the previous network library it worked out of the box. Is this the same problem of Alexandre? is there an issue in the bugtracket? can we integrated? is there a workarround so that I can continue using my image? Thanks Mariano On Fri, May 13, 2011 at 3:43 PM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > I updated Zinc-HTTP and Zinc-Tests from your server. > Running the tests gives me: 151 run, 151 passes, 0 expected failures, 0 > failures, 0 errors, 0 unexpected passes > > Really cool! > > Alexandre > > On 13 May 2011, at 09:39, Sven Van Caekenberghe wrote: > > > > > On 13 May 2011, at 15:24, Alexandre Bergel wrote: > > > >> I use a core 13197. Running Zinc tests gives me: > >> 146 run, 118 passes, 0 expected failures, 28 failures, 0 errors, 0 > unexpected passes > > > > For all tests to pass, you need the very latest version (160) where the > proxy is bypassed for localhost. > > Also, make sure no other ZnServers are running (they would block the 1701 > port needed by the tests). > > > > Sven > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > -- Mariano http://marianopeck.wordpress.com

May 16, 2011

Re: [Pharo-project] XML maintainer??? Fwd: [Pharo-bugtracker] Issue 4232 in pharo: Failing Tests in Full: XML

by Mariano Martinez Peck

Name: ConfigurationOfPharo-MarianoMartinezPeck.171 Author: MarianoMartinezPeck Time: 16 May 2011, 9:28:34 am UUID: 8425d056-6119-403e-aaf1-07078d6b294d Ancestors: ConfigurationOfPharo-MarianoMartinezPeck.170 XMLSupport was removed from PharoDev On Sun, May 15, 2011 at 11:14 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > So...we added XML to PharoDev. Where are the maintaners? Could you please > check these issues? > > Thanks! > > mariano > > ---------- Forwarded message ---------- > From: <pharo(a)googlecode.com> > Date: Sun, May 15, 2011 at 8:50 PM > Subject: [Pharo-bugtracker] Issue 4232 in pharo: Failing Tests in Full: XML > To: pharo-bugtracker(a)lists.gforge.inria.fr > > > Status: Accepted > Owner: marcus.d...(a)gmail.com > Labels: Milestone-1.3-DevImage > > New issue 4232 by marcus.d...(a)gmail.com: Failing Tests in Full: XML > http://code.google.com/p/pharo/issues/detail?id=4232 > > XML.Tests.Parser.Nodes.XMLObservableListTest.testReplaceFromToWithStartingAt >>>> 0.0 1 >>>> >>>> XML.Tests.Parser.Nodes.XMLOrderedListTest.testReplaceFromToWithStartingAt >>>> >>> > > _______________________________________________ > Pharo-bugtracker mailing list > Pharo-bugtracker(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker > > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

May 16, 2011

Re: [Pharo-project] Amazon AWS S3 Monticello Mirror

by Marcus Denker

On May 15, 2011, at 11:12 PM, StÃ©phane Ducasse wrote: > thanks this is an excellent initiative. > Marcus will love that. > Yes! We should get that setup... very nice! Whose Amazon Account do we use? Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 16, 2011

[Pharo-project] [TODO] Bug Tracker Status (429)

by Marcus Denker

Hello! The weekly bug tracker status report. Open Issues: 429 http://code.google.com/p/pharo/issues/list For starters, looking at the ones tagged "1.3" is best: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.3 These should contain only things -> that are real show stoppers for a release -> We *really* *really* want them -> failing tests -> things that look good that only need to be integrated Another good starting point are issues tagged "easy": http://code.google.com/p/pharo/issues/list?can=2&q=difficulty=Easy -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 16, 2011

Re: [Pharo-project] Zinc in PharoDev (was Re: XML maintainer???)

by Mariano Martinez Peck

On Mon, May 16, 2011 at 8:21 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > On May 16, 2011, at 3:03 AM, GermÃ¡n Arduino wrote: > > > Hi: > > > > I saw in your image that Zinc is already loaded. > > > > It will be at this way in the images from now? I'm asking because I > > must decide what path take with XMLRPC. If Zinc will be the default to > > use, I will adapt xmlrpc to work with Zn. > > yes zinc will be in core. > It is already, you did it ;) > > Stef > > > > > I know that xmlrpc is not heavily used but still I think is cool > > having the tools in the image to expose an easy and straightforward > > API. > > > > I wait comments. > > > > Cheers. > > GermÃ¡n. > > > > > > 2011/5/15 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> So...we added XML to PharoDev. Where are the maintaners? Could you > please > >> check these issues? > >> > >> Thanks! > >> > >> mariano > >> > >> ---------- Forwarded message ---------- > >> From: <pharo(a)googlecode.com> > >> Date: Sun, May 15, 2011 at 8:50 PM > >> Subject: [Pharo-bugtracker] Issue 4232 in pharo: Failing Tests in Full: > XML > >> To: pharo-bugtracker(a)lists.gforge.inria.fr > >> > >> > >> Status: Accepted > >> Owner: marcus.d...(a)gmail.com > >> Labels: Milestone-1.3-DevImage > >> > >> New issue 4232 by marcus.d...(a)gmail.com: Failing Tests in Full: XML > >> http://code.google.com/p/pharo/issues/detail?id=4232 > >> > >>>>> > >>>>> > XML.Tests.Parser.Nodes.XMLObservableListTest.testReplaceFromToWithStartingAt > >>>>> 0.0 1 > >>>>> > >>>>> > XML.Tests.Parser.Nodes.XMLOrderedListTest.testReplaceFromToWithStartingAt > >> > >> > >> _______________________________________________ > >> Pharo-bugtracker mailing list > >> Pharo-bugtracker(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker > >> > >> > >> > >> -- > >> Mariano > >> http://marianopeck.wordpress.com > >> > >> > > > > > -- Mariano http://marianopeck.wordpress.com

May 16, 2011

[Pharo-project] [TODO] 1.3

by Marcus Denker

Core ==== Open Issues: 20 http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3 Failing Tests: 1 https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/lastCompleted… Full === Open Issues: 8 http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3-DevImage Failing Tests: 3 https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/lastCompletedBuild/t… => Most important next Issue to tackle: Get all tests green. It would be nice to get both Core and Full green. Than the idea is that in the spirit of Continuous Delivery, we just keep it green. No degeneration of trivial problems (undeclards), fast roll-back of problematic changes... The idea is to keep it in a state that we could, at a minumum, always say "We could release next Friday". And the best would be: "We could release today". -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 16, 2011

[Pharo-project] [TODO] 1.2.2

by Marcus Denker

Core ----- -> All Tests Green -> No known Bugs reported -> Version number set to 1.2.2 -> New pre-build uploaded, will be linked as current stable core soon. >From now on, 1.2 will stay in "release" mode, we will just fix bugs that happen, but there will be no dedicted "1.2.3" release. (For 1.3, we will do the same: no point release, just an eternal stream of bug fixes in 1.3 Release The version number is just 1.3 plus the update number, that's enough) Full ---- Failing Tests: 4 Open Bugs: 1 http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2.2-DevImage Issue 4166: Failing Tests: OBFakeBrowserTest (ConfigurationOfOmniBrowser needs update) So somone needs to take the current 1.3 of OB Metacello and sync the 1.2 config to load the same packaged. Should not be hard to do. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 16, 2011