August 2018 - Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #1150: 21852-Should-add-a-nice-comment-to-FileStream-to-help-migration

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1150 was: SUCCESS. The Pull Request #1654 was integrated: "21852-Should-add-a-nice-comment-to-FileStream-to-help-migration" Pull request url: https://github.com/pharo-project/pharo/pull/1654 Issue Url: https://pharo.fogbugz.com/f/cases/21852 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 1, 2018

Problem with Iceberg and Working Branches

by Eric Gade

I have already mentioned some of this on Discord so forgive me for being redundant if you've seen it. I'm having problems loading into the latest P7 images from Launcher a working branch of Pharo that I have forked. I perform the following steps: 1. "Repair" the missing local repository for Pharo and load from my forked version on Github 2. Now in the "detached working copy" state, I repair again 3. This time I select "Discard local changes and checkout existing branch". I select my working branch from the remotes 4. It will attempt to load, but eventually a popup appears (not a normal error) that simply says "origin: Error" and "Assertion failed". I'm not sure what's going on, since this procedure seemed to work a week or so ago if I remember correctly. As of a couple of days ago I can no longer load (ie work on) my working branch. I figure I'm doing something wrong, but need to know what. -- Eric

Aug. 1, 2018

[Pharo 7.0-dev] Build #1149: 22288-The-changes-in-21855-affect-old-extension-methods-that-are-not-case-equals

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1149 was: SUCCESS. The Pull Request #1663 was integrated: "22288-The-changes-in-21855-affect-old-extension-methods-that-are-not-case-equals" Pull request url: https://github.com/pharo-project/pharo/pull/1663 Issue Url: https://pharo.fogbugz.com/f/cases/22288 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 1, 2018

Re: [Pharo-dev] CI Issue on PR

by Guillermo Polito

Just FYI, Pablo has answered in the PR. In short, adding new packages means adding them also in the baselines, otherwise metacello does not load them. On Wed, Aug 1, 2018 at 6:48 AM Eric Gade <eric.gade(a)gmail.com> wrote: > Hello all, > > I'm having a strange issue with CI on my recent pull request. See > https://github.com/pharo-project/pharo/pull/1666#issuecomment-409431721 > > The short if it is that tests are failing because it seems some of the new > classes I created are not being loaded into whatever CI is doing. Those > classes are clearly in the commits however. Not sure how to handle this. > It's entirely possible I messed up a part of this process. > > Any suggestions? > > -- > Eric > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Aug. 1, 2018

[Pharo 7.0-dev] Build #1148: 22287-size-t-type-does-not-have-right-size-in-windows-64bit

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1148 was: SUCCESS. The Pull Request #1660 was integrated: "22287-size-t-type-does-not-have-right-size-in-windows-64bit" Pull request url: https://github.com/pharo-project/pharo/pull/1660 Issue Url: https://pharo.fogbugz.com/f/cases/22287 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 1, 2018

CI Issue on PR

by Eric Gade

Hello all, I'm having a strange issue with CI on my recent pull request. See https://github.com/pharo-project/pharo/pull/1666#issuecomment-409431721 The short if it is that tests are failing because it seems some of the new classes I created are not being loaded into whatever CI is doing. Those classes are clearly in the commits however. Not sure how to handle this. It's entirely possible I messed up a part of this process. Any suggestions? -- Eric

Aug. 1, 2018