May 2019 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Calypso idea - inherited tests

by ducasse

> On 29 May 2019, at 23:58, Ben Coman <btc(a)openinworld.com> wrote: > > > > On Thu, 30 May 2019 at 06:26, Denis Kudriashov <dionisiydk(a)gmail.com <mailto:dionisiydk@gmail.com>> wrote: > Hi Ben. > > There are already two features that support inherited tests: > - run all tests using class icon: there will be extra red method group "broken tests" which will show failed inherited tests. > - toggle inheritance visibility with checkbox in third panel: you will see inherited tests and standard method icon will run them. > > Ahh, excellent... the second is exactly what I wanted. > > Although using TestDelaySemaphoreSchedulerMicrosecondTicker as an example, > clicking on a test gives me an error "#selected was sent to nil" in "ClyBrowserToolMorph>>isTabSelected" > Do you get the same? Yes this happens to me often. I think that calypso forks too many processes. > > cheers -ben >

May 30, 2019

[Pharo 8.0] Build #304: 3432-RBMethodNodetempnames-is-used-in-the-build

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

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

May 30, 2019

[Pharo 8.0] Build #303: 3431-Random-calypso-errors-on-class-selection

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

There is a new Pharo build available! The status of the build #303 was: SUCCESS. The Pull Request #3440 was integrated: "3431-Random-calypso-errors-on-class-selection" Pull request url: https://github.com/pharo-project/pharo/pull/3440 Issue Url: https://github.com/pharo-project/pharo/issues/3431 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 30, 2019

[Pharo 8.0] Build #302: Fix minor spelling and grammar issues in RBSearchingLiteralRule

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

There is a new Pharo build available! The status of the build #302 was: SUCCESS. The Pull Request #3439 was integrated: "Fix minor spelling and grammar issues in RBSearchingLiteralRule" Pull request url: https://github.com/pharo-project/pharo/pull/3439 Issue Url: https://github.com/pharo-project/pharo/issues/fix Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 30, 2019

Re: [Pharo-dev] FW: Versioning with Iceberg

by Tim Mackinnon

Hi - Iâm rather confused reading your thread as itâs not clear what youâre doing. Using iceberg - I typically see the normal loading progress bars for long operations on the top left of the screen - often they stack below one another to show nested operations (aside: they are a bit ugly - but itâs a consistent metaphor across Pharo). I get them when loading, pulling, pushing, diffing etc. Do you not see them? Back to your version question - what baseline are you loading from a repo? A specific example might help. If i were to load Exercism as an example - the following page describes how to upgrade to a specific version of the baseline in the repo. Eg latest vs v0.2.3 https://github.com/exercism/pharo-smalltalk/blob/master/docs/UPGRADE.md This describes how to do it in the playground - as versions are actually loaded by metacello - and Iceberg builds on top of it to route things via git and make use of version tags etc, and it then gives the push/pull/commit operations. (Iâm probably describing this badly - but I suspect the confusion is in here for you). Having loaded your particular baseline (the code tagged as v2.0.3 for example), Iceberg will let you compare it to other branches - or hash versions in git. But typically, libraries you use will give you a playground script that specifies a stable version - you eval that in your playground and those libraries will then appear in your image (and also in Iceberg). For your project - you can formalise those dependencies by creating your own baseline that references those scripts as well. But maybe you can describe better what you are doing and we can unpick what is happening. Tim Sent from my iPhone > On 30 May 2019, at 02:07, Shaping <shaping(a)uurda.org> wrote: > > Sorry, I meant progress bar, not histoâ¦. > > From: Shaping [mailto:shaping@uurda.org] > Sent: Wednesday, May 29, 2019 20:05 > To: 'Pharo Development List' <pharo-dev(a)lists.pharo.org> > Subject: RE: [Pharo-dev] Versioning with Iceberg > > > > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Ben Coman > Sent: Wednesday, May 29, 2019 10:58 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] Versioning with Iceberg > > > > On Wed, 29 May 2019 at 23:08, Shaping <shaping(a)uurda.org> wrote: > Iâm finding 7.0.3 to be more stable. > > How do I load a specific baseline/version with Iceberg? Iâm getting 8.0 by default from the cloned local repo, and I prefer not to merge 7.0.3 with 8.0. There are many differences. I want to commit my image changes locally for now on a 7.0.3. > > > Its not completely clear what you want. > > You can right-click a repo > Metacello > Install baseline of..... > > Or right-click a repo > Repository > Remotes > and select one of those branches to check out. > > I missed the Repository item completely, all this time. I think I was blocking it out mentally because I was already in an Iceberg window that lists repos. The doubling up is confusing and unexpected. So we have Iceberg repos wrapping Git repos? Iâm not sure I have the scheme right. > > Why donât we have the usual wait-cursors appearing on long synchronous actions behind button clicks? These lock up the system for 1 or 2 minutes often. For example, I deleted 20-odd packages the other day and waited 2 minutes for it to finish, wondering why the system was completely unresponsive and showing no indication (no histo; no wait cursor). This happens when cloning a Git repo, too. The histo opens about Â½ second before the about 1-m pull finishes. This happened in the 7.0.3 build. Is there a policy not to use a wait-cursor if not histo is shown? > > Shaping >

May 30, 2019

Re: [Pharo-dev] Calypso idea - inherited tests

by Denis Kudriashov

ÑÑ, 30 Ð¼Ð°Ñ 2019 Ð³. Ð² 04:59, Ben Coman <btc(a)openinworld.com>: > > > On Thu, 30 May 2019 at 06:26, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> Hi Ben. >> >> There are already two features that support inherited tests: >> - run all tests using class icon: there will be extra red method group >> "broken tests" which will show failed inherited tests. >> - toggle inheritance visibility with checkbox in third panel: you will >> see inherited tests and standard method icon will run them. >> > > Ahh, excellent... the second is exactly what I wanted. > > Although using TestDelaySemaphoreSchedulerMicrosecondTicker as an example, > clicking on a test gives me an error "#selected was sent to nil" in > "ClyBrowserToolMorph>>isTabSelected" > Do you get the same? > No I don't have it. I checked on Pharo 7 and latest Pharo 8 > > cheers -ben > >

May 30, 2019

Re: [Pharo-dev] Calypso idea - inherited tests

by Ben Coman

On Thu, 30 May 2019 at 06:26, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi Ben. > > There are already two features that support inherited tests: > - run all tests using class icon: there will be extra red method group > "broken tests" which will show failed inherited tests. > - toggle inheritance visibility with checkbox in third panel: you will see > inherited tests and standard method icon will run them. > Ahh, excellent... the second is exactly what I wanted. Although using TestDelaySemaphoreSchedulerMicrosecondTicker as an example, clicking on a test gives me an error "#selected was sent to nil" in "ClyBrowserToolMorph>>isTabSelected" Do you get the same? cheers -ben

May 30, 2019

FW: Versioning with Iceberg

by Shaping

Sorry, I meant progress bar, not histoâ¦. From: Shaping [mailto:shaping@uurda.org] Sent: Wednesday, May 29, 2019 20:05 To: 'Pharo Development List' <pharo-dev(a)lists.pharo.org> Subject: RE: [Pharo-dev] Versioning with Iceberg From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Ben Coman Sent: Wednesday, May 29, 2019 10:58 To: Pharo Development List <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> > Subject: Re: [Pharo-dev] Versioning with Iceberg On Wed, 29 May 2019 at 23:08, Shaping <shaping(a)uurda.org <mailto:shaping@uurda.org> > wrote: Iâm finding 7.0.3 to be more stable. How do I load a specific baseline/version with Iceberg? Iâm getting 8.0 by default from the cloned local repo, and I prefer not to merge 7.0.3 with 8.0. There are many differences. I want to commit my image changes locally for now on a 7.0.3. Its not completely clear what you want. You can right-click a repo > Metacello > Install baseline of..... Or right-click a repo > Repository > Remotes and select one of those branches to check out. I missed the Repository item completely, all this time. I think I was blocking it out mentally because I was already in an Iceberg window that lists repos. The doubling up is confusing and unexpected. So we have Iceberg repos wrapping Git repos? Iâm not sure I have the scheme right. Why donât we have the usual wait-cursors appearing on long synchronous actions behind button clicks? These lock up the system for 1 or 2 minutes often. For example, I deleted 20-odd packages the other day and waited 2 minutes for it to finish, wondering why the system was completely unresponsive and showing no indication (no histo; no wait cursor). This happens when cloning a Git repo, too. The histo opens about Â½ second before the about 1-m pull finishes. This happened in the 7.0.3 build. Is there a policy not to use a wait-cursor if not histo is shown? Shaping

May 30, 2019

Re: [Pharo-dev] Versioning with Iceberg

by Shaping

From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Ben Coman Sent: Wednesday, May 29, 2019 10:58 To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: Re: [Pharo-dev] Versioning with Iceberg On Wed, 29 May 2019 at 23:08, Shaping <shaping(a)uurda.org <mailto:shaping@uurda.org> > wrote: Iâm finding 7.0.3 to be more stable. How do I load a specific baseline/version with Iceberg? Iâm getting 8.0 by default from the cloned local repo, and I prefer not to merge 7.0.3 with 8.0. There are many differences. I want to commit my image changes locally for now on a 7.0.3. Its not completely clear what you want. You can right-click a repo > Metacello > Install baseline of..... Or right-click a repo > Repository > Remotes and select one of those branches to check out. I missed the Repository item completely, all this time. I think I was blocking it out mentally because I was already in an Iceberg window that lists repos. The doubling up is confusing and unexpected. So we have Iceberg repos wrapping Git repos? Iâm not sure I have the scheme right. Why donât we have the usual wait-cursors appearing on long synchronous actions behind button clicks? These lock up the system for 1 or 2 minutes often. For example, I deleted 20-odd packages the other day and waited 2 minutes for it to finish, wondering why the system was completely unresponsive and showing no indication (no histo; no wait cursor). This happens when cloning a Git repo, too. The histo opens about Â½ second before the about 1-m pull finishes. This happened in the 7.0.3 build. Is there a policy not to use a wait-cursor if not histo is shown? Shaping

May 30, 2019

Re: [Pharo-dev] Versioning with Iceberg

by Shaping

Iâm finding 7.0.3 to be more stable. How do I load a specific baseline/version with Iceberg? Iâm getting 8.0 by default from the cloned local repo, and I prefer not to merge 7.0.3 with 8.0. There are many differences. I want to commit my image changes locally for now on a 7.0.3. Its not completely clear what you want. You can right-click a repo > Metacello > Install baseline of..... Or right-click a repo > Repository > Remotes and select one of those branches to check out. The baselines look specialized. I want Pharo 7.0.3, not just one package. Shaping

May 30, 2019