December 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] TODO for 1.2...

by Tudor Girba

Nice work! Doru On 14 Dec 2010, at 11:09, Marcus Denker wrote: > > On Dec 13, 2010, at 5:54 PM, Marcus Denker wrote: > >> Open Bugs: >> >> http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2 >> > All failing tests now have a bug tracker entry. > > There is now a bug milestone defined for the full image: > > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage > > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it."

Dec. 14, 2010

[Pharo-project] Fwd: [Pharo-users] "Making ToolSet more flexible", any taker?

by Igor Stasenko

On 14 December 2010 09:21, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi guys. I am out of time, but if someone wants to do a nice and not so > difficult contribution to Pharo, is to improve the ToolSet support. > > Issue is here: http://code.google.com/p/pharo/issues/detail?id=1915 > > And discussion is here: > http://forum.world.st/Questions-about-ToolSet-td1460544.html > Actually it's a much more older Â - 2 years http://lists.gforge.inria.fr/pipermail/pharo-project/2008-October/002872.ht… Here is what i proposed to this: http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg02869.ht… > Cheers > > Mariano > -- Best regards, Igor Stasenko AKA sig.

Dec. 14, 2010

Re: [Pharo-project] Issue 2524 in pharo: Debugger code completion should take into account the types of the objects that are actually assigned to variables

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.2-DevImage Comment #4 on issue 2524 by marcus.denker: Debugger code completion should take into account the types of the objects that are actually assigned to variables http://code.google.com/p/pharo/issues/detail?id=2524 (No comment was entered for this change.)

Dec. 14, 2010

Re: [Pharo-project] TODO for 1.2...

by Marcus Denker

On Dec 13, 2010, at 5:54 PM, Marcus Denker wrote: > Open Bugs: > > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2 > All failing tests now have a bug tracker entry. There is now a bug milestone defined for the full image: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Dec. 14, 2010

[Pharo-project] Issue 3416 in pharo: ClosureTests>>#testWhileWithTempIsNil fails

by pharo＠googlecode.com

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2 New issue 3416 by marcus.denker: ClosureTests>>#testWhileWithTempIsNil fails http://code.google.com/p/pharo/issues/detail?id=3416 ClosureTests>>#testWhileWithTempIsNil fails Possibly related to Issue 2360

Dec. 14, 2010

[Pharo-project] Issue 3415 in pharo: Failing tests for SUNit

by pharo＠googlecode.com

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2 New issue 3415 by marcus.denker: Failing tests for SUNit http://code.google.com/p/pharo/issues/detail?id=3415 >>> SUnit.Tests.SUnitTest.testExpectedFailure 0.0 50 >>> SUnit.Tests.SUnitTest.testExpectedFailureDetection 0.0 50 >>> SUnit.Tests.SUnitTest.testExpectedFailurePass 0.0 50 These are testsing the expected failures defined by pragmas that we removed because of performance. Tests should be fixed to use oldstyle expected failure definition

Dec. 14, 2010

Re: [Pharo-project] Issue 3179 in pharo: Failing Tests for Monticello

by pharo＠googlecode.com

Comment #1 on issue 3179 by marcus.denker: Failing Tests for Monticello http://code.google.com/p/pharo/issues/detail?id=3179 Current state: >>> Tests.Monticello.MCChangeNotificationTest.testExtMethodModified 0.0050 >>> 50 >>> Tests.Monticello.MCPackageTest.testUnload 0.636 50 The Tests.Monticello.MCPackageTest.testUnload only fails on Hudson.

Dec. 14, 2010

[Pharo-project] Issue 3414 in pharo: CompilerEvaluationTest>>#testEvaluationOfSelfSend fails

by pharo＠googlecode.com

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2 New issue 3414 by marcus.denker: CompilerEvaluationTest>>#testEvaluationOfSelfSend fails http://code.google.com/p/pharo/issues/detail?id=3414 CompilerEvaluationTest>>#testEvaluationOfSelfSend fails

Dec. 14, 2010

[Pharo-project] Issue 3413 in pharo: WeakFinalizersTest.testNewFinalizationSupported fails on Hudson builder

by pharo＠googlecode.com

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2 New issue 3413 by marcus.denker: WeakFinalizersTest.testNewFinalizationSupported fails on Hudson builder http://code.google.com/p/pharo/issues/detail?id=3413 WeakFinalizersTest.testNewFinalizationSupported fails on Hudson builder Do we need a newer VM?

Dec. 14, 2010

[Pharo-project] Issue 3412 in pharo: Failing test: SmalltalkEditor>>#testCompilationOfUndefinedVar

by pharo＠googlecode.com

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2 New issue 3412 by marcus.denker: Failing test: SmalltalkEditor>>#testCompilationOfUndefinedVar http://code.google.com/p/pharo/issues/detail?id=3412 SmalltalkEditor>>#testCompilationOfUndefinedVar fails. SmalltalkEditor seems to not have an easy to discover API to open an editor on am existing string / paragraph. (at least I could not find it)

Dec. 14, 2010