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

[Pharo-project] pharo-2.0-tests Â» win - Build # 411 - Still Failing!

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

Oct. 15, 2012

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

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

Oct. 15, 2012

[Pharo-project] [update 2.0] #20342

by Marcus Denker

20342 ----- Issue 6815: Free freetype from bugs http://code.google.com/p/pharo/issues/detail?id=6815 Issue 6679: Failing test: ZnHTTPSTests.testPayPal http://code.google.com/p/pharo/issues/detail?id=6679 Issue 6812: Smalltalkhub Monticello Repository throws error when empty http://code.google.com/p/pharo/issues/detail?id=6812 -- Marcus Denker -- http://marcusdenker.de

Oct. 15, 2012

[Pharo-project] How to export multiple Pharo packages to VW

by Stephan Eggermont

The VW5PackageExporter allows the exporting of a package to the VW xml based fileout format. I've adapted the code to be less Seaside-specific, and am now able to export one package (Parasol-Core). If I try to export another package (Parasol-Tests), which depends on the earlier one, it fails to load. It can't resolve the dependency to a superclass defined in Parasol-Core. I've seen that Roassal puts all Pharo packages into one VW package. That would work, but is not very nice. A package in VW doesn't seem to register its dependencies in a fileout. Would creating a parcel help, or should I try something on basis of RPackage? Stephan

Oct. 15, 2012

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

by StÃ©phane Ducasse

On Oct 14, 2012, at 11:56 PM, Alexandre Bergel wrote: >> 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. > It is for gofer tests. > 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. We should incrementally build ups new infrastructure. I'm thinking about object centric debugger for example. > >> >> 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. 15, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 410 - Still Failing!

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

Oct. 15, 2012

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

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

Oct. 15, 2012

[Pharo-project] pharo-2.0-tests Â» mac - Build # 410 - Still Failing!

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

Oct. 15, 2012

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

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

Oct. 15, 2012

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

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

Oct. 15, 2012