- Pharo-dev - lists.pharo.org

[Pharo 9.0] Build #152: Remake PR 5412
by ci-pharo-ci-jenkins2＠inria.fr March 15, 2020

March 15, 2020

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

1 0

[Pharo 8.0] Build #1132: About-Processor-yield--Object--yield-2Version
by ci-pharo-ci-jenkins2＠inria.fr March 15, 2020

March 15, 2020

There is a new Pharo build available! The status of the build #1132 was: SUCCESS. The Pull Request #5412 was integrated: "About-Processor-yield--Object--yield-2Version" Pull request url: https://github.com/pharo-project/pharo/pull/5412 Issue Url: https://github.com/pharo-project/pharo/issues/About Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #151: 5896 detected error in extreme rare cases for slider
by ci-pharo-ci-jenkins2＠inria.fr March 15, 2020

March 15, 2020

There is a new Pharo build available! The status of the build #151 was: FAILURE. The Pull Request #5897 was integrated: "5896 detected error in extreme rare cases for slider" Pull request url: https://github.com/pharo-project/pharo/pull/5897 Issue Url: https://github.com/pharo-project/pharo/issues/5896 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #150: Cleanup world
by ci-pharo-ci-jenkins2＠inria.fr March 15, 2020

March 15, 2020

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

1 0

[Pharo 9.0] Build #149: 5895-Flaky-Calypso-tests
by ci-pharo-ci-jenkins2＠inria.fr March 15, 2020

March 15, 2020

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

1 0

[Pharo 9.0] Build #148: Revert "5724-Improve-AdditionalMethodStaterefersToLiteral"
by ci-pharo-ci-jenkins2＠inria.fr March 15, 2020

March 15, 2020

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

1 0

[Pharo 9.0] Build #147: 5779 - Setting Display Scale Factor Changing
by ci-pharo-ci-jenkins2＠inria.fr March 15, 2020

March 15, 2020

There is a new Pharo build available! The status of the build #147 was: SUCCESS. The Pull Request #5889 was integrated: "5779 - Setting Display Scale Factor Changing" Pull request url: https://github.com/pharo-project/pharo/pull/5889 Issue Url: https://github.com/pharo-project/pharo/issues/5779 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #146: Add executable comments in SequenceableCollection - conevrting protocol
by ci-pharo-ci-jenkins2＠inria.fr March 15, 2020

March 15, 2020

There is a new Pharo build available! The status of the build #146 was: FAILURE. The Pull Request #5806 was integrated: "Add executable comments in SequenceableCollection - conevrting protocol" Pull request url: https://github.com/pharo-project/pharo/pull/5806 Issue Url: https://github.com/pharo-project/pharo/issues/Pharo9.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Iceberg confusion
by Ben Coman March 14, 2020

March 14, 2020

So I discovered a bug with Pharo Launcher and logged... https://github.com/pharo-project/pharo-launcher/issues/431 and then wanted to contributing a fix, but hit some confusion with Iceberg that discouraged me continuing. The first thing I'm compelled to do to build my sense of control/mastery of the situation is sync the local github repo to the in-Image code, and I continually struggle with doing this quickly and fluently. In a fresh install of Pharo Launcher (pharo-launcher-1.9.2.zip), after opening Iceberg and on the pharo-launcher repo doing Repair > Clone again this repository > Clone from github.com + Owner Name: pharo-project + Project Name: pharo-launcher I find it is "not-yet" repaired. There is more-to-do [1] to repair a "Detach Working Copy" [image: image.png] A newcomer confronted with that may just stop there but I'm familiar with Iceberg so IIUC to clear a "Detached Working Copy" I need to do checkout a commit. So I try... Right-click pharo-launcher > Repository... [image: image.png] But that doesn't help me since there is no clue which commit the in-Image code came from**, so I don't know which to check out. I presume the middle tab at the bottom is showing the diff between "a49ef1d to HEAD" on disk and not the in-Image source. If I take a guess to check out the latest then that shows a lot of difference, so that is discouraging. I really don't want to have to try checking out each commit in turn searching for the matching one. Now luckily half an hour later while writing this post I notice there is a "1.9.2" tag. Checking this out gave now differences so yay! I managed to work around my problem. But still, I lost that half-hour (and similar many times before) so my Big Question still remains... Why must information about where there code comes always from be deleted from release-images??? Above I had prior knowledge to to fill in the "Repair" fields with + Owner Name: pharo-project + Project Name: pharo-launcher but other times having to research-and-guess what these fields should be to match in-Image code is a real barrier to contributing. It would be really-really great if rather than an image being delivered like this... [image: image.png] it would look like this... [image: image.png] with all the other Unknowns also filled in, but discovering that info would take another half hour (also a case in point) This would make it simple to fill in the Repair dialog fields, and remove my main workflow irritation in an otherwise fantastic tool. cheers -ben

2 1

[Pharo 9.0] Build #145: Bug in the comparison of CompiledMethods
by ci-pharo-ci-jenkins2＠inria.fr March 13, 2020

March 13, 2020

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

1 0