- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3477 in pharo: Should not we remove TextLink, TextURL and friends?
by pharo＠googlecode.com Dec. 22, 2010

Dec. 22, 2010

Status: Accepted Owner: stephane.ducasse Labels: Milestone-1.3 New issue 3477 by stephane.ducasse: Should not we remove TextLink, TextURL and friends? http://code.google.com/p/pharo/issues/detail?id=3477 or at least understand well the references.

1 0

[Pharo-project] Issue 3452 in pharo: GlorpDBX no longer loads due to garbled timestamp
by pharo＠googlecode.com Dec. 22, 2010

Dec. 22, 2010

Status: New Owner: ---- New issue 3452 by ya...@rogers.com: GlorpDBX no longer loads due to garbled timestamp http://code.google.com/p/pharo/issues/detail?id=3452 Pharo image: Pharo-core Pharo core version: PharoCore-1.2-12251 is OKAY, but PharoCore-1.2-12261 and newer fails Steps to reproduce: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfGlorpDBX'; load. ! ConfigurationOfGlorpDBX ensureMetacello. ! (ConfigurationOfGlorpDBX project version: '1.2') load: { 'All with PostgreSQL native'. } I tried to debug it myself, but ended up in method trailer code. I also tried reverting the method #parseTimestampFrom: and got a complaint about "<historical>", which I couldn't figure out where it came from. Attachments: PharoDebug.log 40.3 KB

1 9

[Pharo-project] Issue 3418 in pharo: MessageTallyTest>>#testTallySends is failing
by pharo＠googlecode.com Dec. 22, 2010

Dec. 22, 2010

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2 New issue 3418 by marcus.denker: MessageTallyTest>>#testTallySends is failing http://code.google.com/p/pharo/issues/detail?id=3418 MessageTallyTest.testTallySends

1 1

[Pharo-project] Issue 3474 in pharo: BmpReadWriterPlugin primitives should be used
by pharo＠googlecode.com Dec. 22, 2010

Dec. 22, 2010

Status: Accepted Owner: Torsten....@astares.de Labels: Type-Squeak New issue 3474 by Torsten....@astares.de: BmpReadWriterPlugin primitives should be used http://code.google.com/p/pharo/issues/detail?id=3474 Andreas wrote: "For some strange reasons the BMP read/write primitives weren't enabled. Probably an oversight on my behalf. The primitives improve performance by 10-20x" Code: http://lists.squeakfoundation.org/pipermail/squeak-dev/2010-December/156042… Test adoption: http://lists.squeakfoundation.org/pipermail/squeak-dev/2010-December/156043… Discussion: http://lists.squeakfoundation.org/pipermail/vm-dev/2010-December/006199.html

1 2

Re: [Pharo-project] Issue 3442 in pharo: Debugger Tests
by pharo＠googlecode.com Dec. 22, 2010

Dec. 22, 2010

Updates: Summary: Debugger Tests Comment #1 on issue 3442 by stephane.ducasse: Debugger Tests http://code.google.com/p/pharo/issues/detail?id=3442 (No comment was entered for this change.)

1 2

[Pharo-project] Issue 3475 in pharo: Finder insensitive selector/class researches
by pharo＠googlecode.com Dec. 22, 2010

Dec. 22, 2010

Status: Fixed Owner: Benjamin.VanRyseghem.Pharo New issue 3475 by Benjamin.VanRyseghem.Pharo: Finder insensitive selector/class researches http://code.google.com/p/pharo/issues/detail?id=3475 Now, the selector and class researches in Finder are case insensitive. Posted in PharoTaskForces and PharoInbox

1 1

[Pharo-project] Issue 3476 in pharo: ToolsTest.MessageTally.MessageTallyTest.testTallySends is now green
by pharo＠googlecode.com Dec. 22, 2010

Dec. 22, 2010

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

1 2

Re: [Pharo-project] Issue 2232 in pharo: digitValue speed up part one and two.
by pharo＠googlecode.com Dec. 22, 2010

Dec. 22, 2010

Comment #8 on issue 2232 by marcus.denker: digitValue speed up part one and two. http://code.google.com/p/pharo/issues/detail?id=2232 Next Action: -> What exactly means "first part is in?" -> Define what is left to do.

1 2

[Pharo-project] [TODO] 1.2 Core + Full
by Marcus Denker Dec. 22, 2010

Dec. 22, 2010

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.

6 6

Dec. 22, 2010

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. Stef

4 5