October 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] pharo-2.0-tests Â» linux - Build # 409 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Oct. 15, 2012

[Pharo-project] [Issue Tracker] Issues that need a human review

by Marcus Denker

Issues tagged "HumanReviewNeeded" Just 9 open! http://code.google.com/p/pharo/issues/list?can=2&q=status%3AHumanReviewNeed… These need to be checked. Look at the code. Test it a bit. Then decide: What still needs to be done? Or maybe it is already ready to be added? Marcus -- Marcus Denker -- http://marcusdenker.de

Oct. 15, 2012

[Pharo-project] [Issue Tracker] Currently failing tests

by Marcus Denker

For both 1.4 and 2.0: 7 open issues: http://code.google.com/p/pharo/issues/list?can=2&q=Status%3DFailingTest -- Marcus Denker -- http://marcusdenker.de

Oct. 15, 2012

[Pharo-project] [update 2.0] #20341

by Marcus Denker

20341 ----- Issue 6804: JobProgressMorph has two undeclared iVars http://code.google.com/p/pharo/issues/detail?id=6804 -- Marcus Denker -- http://marcusdenker.de

Oct. 15, 2012

Re: [Pharo-project] Idea for finding bugs/profiling...

by Alexandre Bergel

> would it not be possible to run and trace automatically the same tests in 1.4 and 2.0 and see the delta? > because this would help us a lot of understand the differences. For which tests and which applications? All the Pharo tests? That could easily be done if we stay away from tracing the kernel and collections. Method Wrapper would easily do the thing. > > For example, I trying to fix the Gofer unload behavior and I'm stepping step by step in 1.4 and 2.0. > Having some support would really help. > > Stef -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 14, 2012

Re: [Pharo-project] EncryptedMultiDisplayScanner, are you serious?

by Igor Stasenko

On 14 October 2012 22:21, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Oct 14, 2012, at 10:15 PM, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: > >> On 14.10.2012 10:52, phil(a)highoctane.be wrote: >>> I am always feeling like an archaelogist when looking at these things... >>> >>> Phil >> Funnily enough, that class in particular was added just half a year ago :) >> > > Yes, and as always, I am guilty of having integrated that change :-) > Quality control needs more manpower than we currently have. Aside of tools which can help with it. Why we can't use monkey to generate diffs? It should be straightforward. > > Marcus > > -- > Marcus Denker -- http://marcusdenker.de -- Best regards, Igor Stasenko.

Oct. 14, 2012

Re: [Pharo-project] EncryptedMultiDisplayScanner, are you serious?

by StÃ©phane Ducasse

Yes it means that we can also fix our own error. This is also why I would like to see the diff when the code is committed. I checked today ss3 but I could only see the rss and not the diff. Setf > On 14.10.2012 10:52, phil(a)highoctane.be wrote: >> I am always feeling like an archaelogist when looking at these things... >> >> Phil > Funnily enough, that class in particular was added just half a year ago :) > > Cheers, > Henry >

Oct. 14, 2012

Re: [Pharo-project] Idea for finding bugs/profiling...

by StÃ©phane Ducasse

Another idea would be to be able to provide an expression and to know when in the trace this expression is false or true For example I would like to know when the classes are unloaded exactly. So I could run a test and ask tell me from which invocation this expression is false. And I would know immediately what is the expression correctly removing classes and I could compare. Stef On Oct 14, 2012, at 10:44 PM, StÃ©phane Ducasse wrote: > Hi alex > > would it not be possible to run and trace automatically the same tests in 1.4 and 2.0 and see the delta? > because this would help us a lot of understand the differences. > > For example, I trying to fix the Gofer unload behavior and I'm stepping step by step in 1.4 and 2.0. > Having some support would really help. > > Stef

Oct. 14, 2012

[Pharo-project] Idea for finding bugs/profiling...

by StÃ©phane Ducasse

Hi alex would it not be possible to run and trace automatically the same tests in 1.4 and 2.0 and see the delta? because this would help us a lot of understand the differences. For example, I trying to fix the Gofer unload behavior and I'm stepping step by step in 1.4 and 2.0. Having some support would really help. Stef

Oct. 14, 2012

Re: [Pharo-project] EncryptedMultiDisplayScanner, are you serious?

by Marcus Denker

On Oct 14, 2012, at 10:15 PM, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: > On 14.10.2012 10:52, phil(a)highoctane.be wrote: >> I am always feeling like an archaelogist when looking at these things... >> >> Phil > Funnily enough, that class in particular was added just half a year ago :) > Yes, and as always, I am guilty of having integrated that change :-) Marcus -- Marcus Denker -- http://marcusdenker.de

Oct. 14, 2012