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

[Pharo 7.0-dev] Build #1151: 22289-Pharo-bootstrap-stopped-to-be-repository-agnostic
by ci-pharo-ci-jenkins2＠inria.fr Aug. 1, 2018

Aug. 1, 2018

There is a new Pharo build available! The status of the build #1151 was: SUCCESS. The Pull Request #1664 was integrated: "22289-Pharo-bootstrap-stopped-to-be-repository-agnostic" Pull request url: https://github.com/pharo-project/pharo/pull/1664 Issue Url: https://pharo.fogbugz.com/f/cases/22289 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Problem with Iceberg and Working Branches
by Eric Gade Aug. 1, 2018

Aug. 1, 2018

Ok, so when I follow these steps: - load your fork - create *new* branch from image - merge your old branch into this new one I get the same kind of error I was reporting above. While the previous email with the Fuel dump awaits mod approval, I'll just attach this screenshot so you can see what I mean On Wed, Aug 1, 2018 at 8:02 AM, Eric Gade <eric.gade(a)gmail.com> wrote: > Here is the fuel dump of the stack (attached) > > On Wed, Aug 1, 2018 at 8:01 AM, Eric Gade <eric.gade(a)gmail.com> wrote: > >> Every week some tenths of pull requests are integrated in Pharo, so >>> loading the Pharo7 image of today will give you an image compleeetely >>> different from the one you worked with one week ago. >>> >> >> This is something I'm used to from the non-Pharo Git world. Normally I >> would do what it called "rebasing," which essentially replays any commits >> on my branch atop the HEAD of the current master branch. In cases where you >> know that the things you're working on are unlikely to have changed in the >> meantime, this tends to work most of the time. >> >> >>> For your particular use case (have a new image and want to keep working >>> on an old pharo branch), I'd suggest that instead of doing "Discard >>> local changes and checkout existing branch" you do >>> >> >> I'll give this a shot in a little bit and let you know if it works. >> >> >>> You have the popup with the "Ignore" and "Debug" options? Could you >>> click on "Debug" and share your stack trace? >>> >> >> No. This is not the normal error popup. It's more like a little dialog >> that only has text and an OK button. However, I was able to go into the >> repository via Iceberg and attempt to checkout the branch from origin >> directly. That did give me a normal error and I do have a fuel dump of the >> stack. Unfortunately it is too big to attach to emails to this list. >> >> I will send a follow up message with the attachment, but it will need mod >> approval. >> >> On Wed, Aug 1, 2018 at 7:52 AM, Guillermo Polito < >> guillermopolito(a)gmail.com> wrote: >> >>> Ah, just in case I add to what I say: this particular tricky scenario is >>> specific for Pharo and contributing to Pharo. >>> >>> Any third party project/library will not have the constraints described >>> in my previous email. >>> >>> On Wed, Aug 1, 2018 at 1:48 PM Guillermo Polito < >>> guillermopolito(a)gmail.com> wrote: >>> >>>> Hi! >>>> >>>> On Wed, Aug 1, 2018 at 1:30 PM Eric Gade <eric.gade(a)gmail.com> wrote: >>>> >>>>> 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: >>>>> >>>> >>>> I'll try to reproduce it, but meanwhile. >>>> >>>> >>>>> 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 >>>>> >>>> >>>> I have a remark on this step, that should be known and understood by >>>> people contributing Pharo. >>>> - When you download an image, that image knows from which commit it was >>>> built. This is done on purpose so then you can continue working from >>>> exactly that commit (less merge problems, do not need to update your live >>>> image...). >>>> - Every week some tenths of pull requests are integrated in Pharo, so >>>> loading the Pharo7 image of today will give you an image compleeetely >>>> different from the one you worked with one week ago. >>>> >>>> What this means, is that if you checkout an old branch, Iceberg will >>>> try to "downgrade" all your packages to your branch's version, and that may >>>> not always work, because while updating pharo packages you may break >>>> running code and running instances (take into account you have several >>>> processes running). This is the same problem of the old "Software update" >>>> option in Pharo that was deprecated and removed some time ago already. And >>>> this is why in general we do not recommend nowadays to update a pharo image >>>> through iceberg, because you cause a kind of self brain-surgery scenario. >>>> >>>> This is why also we DO recommend, when you start with a new image to >>>> "create a new branch from the image commit". Because this option makes you >>>> work on a branch that is 100% in sync with your Pharo image and it will >>>> just simplify your life :). >>>> >>>> For your particular use case (have a new image and want to keep working >>>> on an old pharo branch), I'd suggest that instead of doing "Discard >>>> local changes and checkout existing branch" you do >>>> - load your fork >>>> - create *new* branch from image >>>> - merge your old branch into this new one >>>> >>>> That will be by far less disruptive. >>>> >>>> >>>>> 4. It will attempt to load, but eventually a popup appears (not a >>>>> normal error) that simply says "origin: Error" and "Assertion failed". >>>>> >>>> >>>> You have the popup with the "Ignore" and "Debug" options? Could you >>>> click on "Debug" and share your stack trace? >>>> >>>> >>>>> >>>>> 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. >>>>> >>>> >>>> Well, this is for sure related to what I described above, using a new >>>> image with an old branch.... >>>> >>>> >>>>> >>>>> I figure I'm doing something wrong, but need to know what. >>>>> >>>> >>>> Maybe not, and it's just a matter of a complex scenario + an unexpected >>>> case in iceberg (thus the assertion). >>>> >>>> Keep us updated to see if we can help you, >>>> Guille >>>> >>> >>> >>> -- >>> >>> >>> >>> 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 >>> >> >> >> >> -- >> Eric >> > > > > -- > Eric > -- Eric

1 0

[Pharo 7.0-dev] Build #1150: 21852-Should-add-a-nice-comment-to-FileStream-to-help-migration
by ci-pharo-ci-jenkins2＠inria.fr Aug. 1, 2018

Aug. 1, 2018

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…

1 0

[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 Aug. 1, 2018

Aug. 1, 2018

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…

1 0

CI Issue on PR
by Eric Gade Aug. 1, 2018

Aug. 1, 2018

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

2 1

[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 Aug. 1, 2018

Aug. 1, 2018

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…

1 0