- Pharo-dev - lists.pharo.org

Iceberg Loading issue
by Vincent.Blondeau＠lamresearch.com Jan. 26, 2018

Jan. 26, 2018

Hi, I am encountering some problems with Iceberg on the latest version. I want to load the commits I just made on a branch on my Pharo fork, let's say "21124". I set the local repo to the current version of my Pharo image, i.e. the development branch (commit 0dbf86). Thanks to the iceberg interface, I change the current branch to "21124", there are 12 commits that are incoming. Then, I then do "Pull incoming commit" to load them. But after a few moment, instead of loading only the delta between the development branch and the "21124" one, iceberg goes further in the commit history and wants to load 174 commits... Including one that does not load. By debugging, it seems that there is a problem with LGitRepository>>fastForward:, the result of "self lookup: 'FETCH_HEAD'" gives not the good commit i.e. the one of the development branch (commit 0dbf86), but instead the one of "I do not what". Does this issue is known? And how can I bypass it or solve it? Thanks, Vincent

4 4

[Pharo 7.0-dev] Build #462: 20757-Playground-should-be-extensible-as-GT-Inspector
by ci-pharo-ci-jenkins2＠inria.fr Jan. 26, 2018

Jan. 26, 2018

There is a new Pharo build available! The status of the build #462 was: SUCCESS. The Pull Request #745 was integrated: "20757-Playground-should-be-extensible-as-GT-Inspector" Pull request url: https://github.com/pharo-project/pharo/pull/745 Issue Url: https://pharo.fogbugz.com/f/cases/20757 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #461: 21110 Super tearDown need to be called as last message in tearDown ofâ¦
by ci-pharo-ci-jenkins2＠inria.fr Jan. 26, 2018

Jan. 26, 2018

There is a new Pharo build available! The status of the build #461 was: SUCCESS. The Pull Request #722 was integrated: "21110 Super tearDown need to be called as last message in tearDown ofâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/722 Issue Url: https://pharo.fogbugz.com/f/cases/21110 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #460: 21108 Super tearDown need to be called as last message in tearDown of RGMethodDefinitionTest
by ci-pharo-ci-jenkins2＠inria.fr Jan. 26, 2018

Jan. 26, 2018

There is a new Pharo build available! The status of the build #460 was: SUCCESS. The Pull Request #723 was integrated: "21108 Super tearDown need to be called as last message in tearDown of RGMethodDefinitionTest" Pull request url: https://github.com/pharo-project/pharo/pull/723 Issue Url: https://pharo.fogbugz.com/f/cases/21108 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #459: 21107 Super tearDown need to be called as last message in tearDown of RBRefactoringTest
by ci-pharo-ci-jenkins2＠inria.fr Jan. 26, 2018

Jan. 26, 2018

There is a new Pharo build available! The status of the build #459 was: FAILURE. The Pull Request #724 was integrated: "21107 Super tearDown need to be called as last message in tearDown of RBRefactoringTest" Pull request url: https://github.com/pharo-project/pharo/pull/724 Issue Url: https://pharo.fogbugz.com/f/cases/21107 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #458: 20905-upToAll-for-ZnCharacterReadStream
by ci-pharo-ci-jenkins2＠inria.fr Jan. 26, 2018

Jan. 26, 2018

There is a new Pharo build available! The status of the build #458 was: SUCCESS. The Pull Request #634 was integrated: "20905-upToAll-for-ZnCharacterReadStream" Pull request url: https://github.com/pharo-project/pharo/pull/634 Issue Url: https://pharo.fogbugz.com/f/cases/20905 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #457: 21121-Use-assertequals-in-TimespanTest
by ci-pharo-ci-jenkins2＠inria.fr Jan. 26, 2018

Jan. 26, 2018

There is a new Pharo build available! The status of the build #457 was: SUCCESS. The Pull Request #743 was integrated: "21121-Use-assertequals-in-TimespanTest" Pull request url: https://github.com/pharo-project/pharo/pull/743 Issue Url: https://pharo.fogbugz.com/f/cases/21121 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #456: 20057-Autocomplete-crashes-for-trait-methods
by ci-pharo-ci-jenkins2＠inria.fr Jan. 26, 2018

Jan. 26, 2018

There is a new Pharo build available! The status of the build #456 was: SUCCESS. The Pull Request #707 was integrated: "20057-Autocomplete-crashes-for-trait-methods" Pull request url: https://github.com/pharo-project/pharo/pull/707 Issue Url: https://pharo.fogbugz.com/f/cases/20057 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #455: 21104 Super tearDown need to be called as last message in tearDown of PNGReadWriterTest
by ci-pharo-ci-jenkins2＠inria.fr Jan. 26, 2018

Jan. 26, 2018

There is a new Pharo build available! The status of the build #455 was: SUCCESS. The Pull Request #727 was integrated: "21104 Super tearDown need to be called as last message in tearDown of PNGReadWriterTest" Pull request url: https://github.com/pharo-project/pharo/pull/727 Issue Url: https://pharo.fogbugz.com/f/cases/21104 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Next Pharo release moved to end of year
by Esteban Lorenzano Jan. 26, 2018

Jan. 26, 2018

Hi all, After some analysis of current condition of development, we decided to move the upcoming release to end of the year (and not May, as usual). The reason is that we are taking more time than expected to finish/polish a quantity of things that needs to be finish to call this a âsuccessful releaseâ to make us feel confortable with a release early this year. Thing isâ¦ we were very ambitious with this version, because a lot of small pieces get into position and we decided to act. Now, to deliver a good version, we need to finish them. For example, along with all the stabilisation phase we need to operate on P7 (an usual task for every version), we still need to finish this important changes: - fullblocks as default - vm 64bits: stabilise and add win64 - stateful traits - calypso (and nautilus removal) - iceberg: fix the UI We (the core team and the community) have a deep commitment with the progress of Pharo, and we will continue get things right to make the continue improvement a pleasant experience. Say that, expect new announcement of things finished and ready to test next weeks :) cheers! Esteban

6 6