- Pharo-dev - lists.pharo.org

[Pharo 7.0] Build #175: Backport-5072-MCClassTraitDefinition-should-take-category-into-account-for-equality
by ci-pharo-ci-jenkins2＠inria.fr Nov. 23, 2019

Nov. 23, 2019

There is a new Pharo build available! The status of the build #175 was: FAILURE. The Pull Request #5075 was integrated: "Backport-5072-MCClassTraitDefinition-should-take-category-into-account-for-equality" Pull request url: https://github.com/pharo-project/pharo/pull/5075 Issue Url: https://pharo.fogbugz.com/f/cases/Backport Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1005: Improve-AssertEquals-Rule
by ci-pharo-ci-jenkins2＠inria.fr Nov. 22, 2019

Nov. 22, 2019

There is a new Pharo build available! The status of the build #1005 was: FAILURE. The Pull Request #5197 was integrated: "Improve-AssertEquals-Rule" Pull request url: https://github.com/pharo-project/pharo/pull/5197 Issue Url: https://github.com/pharo-project/pharo/issues/Improve Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1004: UseNecEntrySubclasses
by ci-pharo-ci-jenkins2＠inria.fr Nov. 22, 2019

Nov. 22, 2019

There is a new Pharo build available! The status of the build #1004 was: FAILURE. The Pull Request #5206 was integrated: "UseNecEntrySubclasses" Pull request url: https://github.com/pharo-project/pharo/pull/5206 Issue Url: https://github.com/pharo-project/pharo/issues/UseNecEntrySubclasses Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1003: Rollback to setStrokePaint for issue: Remove use of StrokePaintCache #5199
by ci-pharo-ci-jenkins2＠inria.fr Nov. 22, 2019

Nov. 22, 2019

There is a new Pharo build available! The status of the build #1003 was: SUCCESS. The Pull Request #5201 was integrated: "Rollback to setStrokePaint for issue: Remove use of StrokePaintCache #5199" Pull request url: https://github.com/pharo-project/pharo/pull/5201 Issue Url: https://github.com/pharo-project/pharo/issues/Pharo8.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1002: #flatCollect: implement using #streamContents:
by ci-pharo-ci-jenkins2＠inria.fr Nov. 22, 2019

Nov. 22, 2019

There is a new Pharo build available! The status of the build #1002 was: SUCCESS. The Pull Request #5204 was integrated: "#flatCollect: implement using #streamContents:" Pull request url: https://github.com/pharo-project/pharo/pull/5204 Issue Url: https://github.com/pharo-project/pharo/issues/flatcollectstreamcontents Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1001: Cleanup #allClassVarNames
by ci-pharo-ci-jenkins2＠inria.fr Nov. 22, 2019

Nov. 22, 2019

There is a new Pharo build available! The status of the build #1001 was: SUCCESS. The Pull Request #5203 was integrated: "Cleanup #allClassVarNames" Pull request url: https://github.com/pharo-project/pharo/pull/5203 Issue Url: https://github.com/pharo-project/pharo/issues/ClassVarnamesCleanup Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1000: Replace-assert-equals-from-non-test-methods
by ci-pharo-ci-jenkins2＠inria.fr Nov. 22, 2019

Nov. 22, 2019

There is a new Pharo build available! The status of the build #1000 was: SUCCESS. The Pull Request #5198 was integrated: "Replace-assert-equals-from-non-test-methods" Pull request url: https://github.com/pharo-project/pharo/pull/5198 Issue Url: https://github.com/pharo-project/pharo/issues/Replace Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

About dashed lines in Athens
by milton mamani Nov. 21, 2019

Nov. 21, 2019

Hi to all I was playing with Athens and I found and error that you can reproduce with the next script in Pharo8x64 macOs ```Smalltalk AthensSurfaceExamples openViewOn: [ :can | can pathTransform restoreAfter: [ can pathTransform translateX: 30 Y: 30. can pathTransform rotateByDegrees: 35. can setPaint: Color red. can setStrokePaint: Color black. can setShape: (-20@ -20 corner: 20@ 20). can draw. ]. ]. AthensSurfaceExamples openViewOn: [ :can | can pathTransform restoreAfter: [ can pathTransform translateX: 30 Y: 30. can pathTransform rotateByDegrees: 35. can setPaint: Color red. (can setStrokePaint: Color black) width: 6; dashes: #(4) offset: 0. can setShape: (-20@ -20 corner: 20@ 20). can draw. ]. ]. AthensSurfaceExamples openViewOn: [ :can | can pathTransform restoreAfter: [ can pathTransform translateX: 30 Y: 30. can pathTransform rotateByDegrees: 35. can setPaint: Color red. can setStrokePaint: Color black. can setShape: (-20@ -20 corner: 20@ 20). can draw. ]. ]. ``` The previous examples opens 3 windows The first the line is normal The second the line is dashed The third one should be normal, but it is dashed Why because there is a cache for the color black in the methods `setStrokePaint:` I think that we need to fix this, Cheers, Milton

1 0

[Pharo 8.0] Build #999: ProtoObject: #mustBeBooleanDeOptimize
by ci-pharo-ci-jenkins2＠inria.fr Nov. 21, 2019

Nov. 21, 2019

There is a new Pharo build available! The status of the build #999 was: FAILURE. The Pull Request #5195 was integrated: "ProtoObject: #mustBeBooleanDeOptimize" Pull request url: https://github.com/pharo-project/pharo/pull/5195 Issue Url: https://github.com/pharo-project/pharo/issues/ProtoObjectmustBeBooleanDeOpt… Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

GildaVM - a Non-Blocking I/O Architecture for the Cog VM
by Ben Coman Nov. 21, 2019

Nov. 21, 2019

I saw an interesting tweet on "GildaVM: a Non-Blocking I/O Architecture for the Cog VM" [1] which shows the VM running multiple interpreter-threads. Where is the paper shown on page 23 available? Side thought, if "usually, 1% of objects survive their first scavenge" [2] as a "breadth-first traversal of objects from the remembered table (a table holding all old objects referencing new objects) and the stack" that implies only a small percentage object mutations were in old space (??) which makes wonder if each interpreter-thread had its "own" new-space, then scavenging each new-space could run independently in parallel-native-threads? Thus a global lock may only(?) be needed to mutate a shared old-space and minimize . This ignores the execution-engine needing to update method-lookup tables. Could native-threads start with their own copy of a warmed up JIT and then work independently? cheers -ben [1] https://www.slideshare.net/esug/gildavm-a-nonblocking-io-architecture-for-t… [2] https://clementbera.wordpress.com/2017/03/12/tuning-the-pharo-garbage-colle…

2 1