- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [TODO] 1.2 Core + Full

by Alexandre Bergel

One test fixed: http://code.google.com/p/pharo/issues/detail?id=3476 Also, it would be cool to have our test on the debugger: http://code.google.com/p/pharo/issues/detail?id=3442 It run green. It is tagged Milestone-1.3. Why not to include it in 1.2? Cheers, Alexandre On 22 Dec 2010, at 04:07, Marcus Denker wrote: > For 1.2 to to be released, we need to > > a) get all tests green. > There are right now 9 failing tests in Core and 9 additional one in the full image. > > 9 of 7915 tests fail: > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/lastCompleted… > > 18 of 10284 tests fail: > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/t… > > some of those are test-server artefacts that only fail on the testserver. > > b) Bug Tracker. Here the issues need to be either resolved or decided to be not show-stoppers > (there will be a 1.3 release! So somehting that is already not in 1.1, why do we need in in 1.2? > A release is just a usable snapshot of an on-going process) > > 23 reports are tagged as 1.2: > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2&colspec=ID… > > 8 reports are tagged as 1.2 for the full image? > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage&c… > > All failing tests do have bug-tracker entries. > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 22, 2010

[Pharo-project] Issue 3476 in pharo: ToolsTest.MessageTally.MessageTallyTest.testTallySends is now green

by pharo＠googlecode.com

Status: Accepted Owner: alexandre.bergel CC: marcus.denker, stephane.ducasse Labels: Difficulty-Easy Milestone-1.2 New issue 3476 by alexandre.bergel: ToolsTest.MessageTally.MessageTallyTest.testTallySends is now green http://code.google.com/p/pharo/issues/detail?id=3476 In a 12284, testTallySends does yellow because one of the method invoked by printString changed. The test has been updated. ToolsTest-AlexandreBergel.denker.13 in the inbox

Dec. 22, 2010

Re: [Pharo-project] about copy in the bug tracker

by George Herolyants

No, you're not the only person experiencing this strange behaviour :). I can reproduce it under Windows using Firefox (Ctrl+C, Alt+C, C only :)), but not Chrome or IE. So it seems like nice bug of google, or Firefox :) George

Dec. 22, 2010

[Pharo-project] Tests for XMLWriter?

by Alexandre Bergel

Hi! Ivan and I tried to use XMLWriter yesterday, but without tests it is a bit cryptic. Are the tests of XMLWriter available somewhere? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 22, 2010

Re: [Pharo-project] about copy in the bug tracker

by Mariano Martinez Peck

On Wed, Dec 22, 2010 at 1:53 PM, Patrick Barroca <patrick.barroca(a)gmail.com>wrote: > no it's not, seems to me a google "shortcut feature" where typing 'c' means > create. > work the same in gmail. no, but in gmail you have press only 'c'. In google code happens when pressing cmd + 'c' (which is the copy paste shortcut). cheers mariano > > > On Wed, Dec 22, 2010 at 12:01 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> >> >> On Wed, Dec 22, 2010 at 11:06 AM, StÃ©phane Ducasse < >> stephane.ducasse(a)inria.fr> wrote: >> >>> Hi guys >>> >>> am i the only one having problem with copy (control-C when on the bug >>> tracker)? >>> I hate when it create a new entry. >>> >> >> no, you are not alone. It happens the same to me. Maybe it is only mac? >> >> >>> >>> Stef >>> >>> >>> >>> >> > > > -- > Patrick Barroca >

Dec. 22, 2010

Re: [Pharo-project] Issue 3447 in pharo: Do we need to menu entry "Shout Workspace"?

by pharo＠googlecode.com

Comment #5 on issue 3447 by guillermopolito: Do we need to menu entry "Shout Workspace"? http://code.google.com/p/pharo/issues/detail?id=3447 Mariano said: Luc, in the cae of 3447, you should commit to the Shout repo since this is not part ofpharo core. BTW....which version of ShoutWorkspace was being installed...because I already fixed that in: Name: ShoutWorkspace.1-maiano.6 Author: maiano Time: 12 May 2010, 7:53:35 pm UUID: 8265a4c8-d212-4ac1-b2d5-79b5722ed9c3 Ancestors: ShoutWorkspace.1-Alexandre_Bergel.5 Removed menuCommandOn: aBuilder from ShoutWorkspace as such item is already in the manu (in the part of most common tools) together with SystemBrowser, Test Runner and Monticello Browser. If they are not there, then they are not under "Tools". cheers Maybe we just have to merge a lost version :)

Dec. 22, 2010

Re: [Pharo-project] [TODO] 1.2 Core + Full

by Alexandre Bergel

Ok, I check the one on MessageTally Alexandre On 22 Dec 2010, at 04:07, Marcus Denker wrote: > For 1.2 to to be released, we need to > > a) get all tests green. > There are right now 9 failing tests in Core and 9 additional one in the full image. > > 9 of 7915 tests fail: > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/lastCompleted… > > 18 of 10284 tests fail: > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/t… > > some of those are test-server artefacts that only fail on the testserver. > > b) Bug Tracker. Here the issues need to be either resolved or decided to be not show-stoppers > (there will be a 1.3 release! So somehting that is already not in 1.1, why do we need in in 1.2? > A release is just a usable snapshot of an on-going process) > > 23 reports are tagged as 1.2: > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2&colspec=ID… > > 8 reports are tagged as 1.2 for the full image? > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage&c… > > All failing tests do have bug-tracker entries. > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 22, 2010

Re: [Pharo-project] about copy in the bug tracker

by Patrick Barroca

no it's not, seems to me a google "shortcut feature" where typing 'c' means create. work the same in gmail. On Wed, Dec 22, 2010 at 12:01 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Wed, Dec 22, 2010 at 11:06 AM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> Hi guys >> >> am i the only one having problem with copy (control-C when on the bug >> tracker)? >> I hate when it create a new entry. >> > > no, you are not alone. It happens the same to me. Maybe it is only mac? > > >> >> Stef >> >> >> >> > -- Patrick Barroca

Dec. 22, 2010

Re: [Pharo-project] Issue 3472 in pharo: Text selection problem in Pharo-dev 1.2

by pharo＠googlecode.com

Updates: Cc: stephane.ducasse Comment #6 on issue 3472 by laurent.laffont: Text selection problem in Pharo-dev 1.2 http://code.google.com/p/pharo/issues/detail?id=3472 Issue 3453 has been merged into this issue.

Dec. 22, 2010

Re: [Pharo-project] PharoCore #12884

by Sven Van Caekenberghe

On 22 Dec 2010, at 10:58, StÃ©phane Ducasse wrote: >> Hi, >> >> I just updated my 1.2 core to #12884 with 3 updates and my MC repos are gone from my packages, only the standard repos remain. >> >> Maybe this is a sign of something that went wrong. > > no this is just that some package where home-orphaned and marcus issued a command to > clean (because you can have duplicate repo with the same name but different password -- > a hell) > and reassign all the package repo to package. So your packages got flushed too apparently. > Sorry. > > Stef >> >> Sven No problem, if this is expected/normal than it is OK for me, Thx, Sven

Dec. 22, 2010