- Pharo-dev - lists.pharo.org

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

Re: [Pharo-dev] Versioning with Iceberg

by Shaping

â¦Trying to have 7.0.3 as my base, not 8.0. Iâm not sure what happened with the VM crash, but I can do without the latest version for now. How do I specify the commit with Iceberg? Shaping From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of ducasse Sent: Wednesday, May 29, 2019 10:17 To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: Re: [Pharo-dev] Versioning with Iceberg Hello Can you tell us what you are doing? Because if a project loads always the head then iceberg will load it. Or you should specify a specific commit. Stef On 29 May 2019, at 11:07, 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. Shaping

May 30, 2019

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

by Denis Kudriashov

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. Is it what you are looking for? or do you need anything else? ÑÑ, 29 Ð¼Ð°Ñ 2019 Ð³., 2:47 Ben Coman <btc(a)openinworld.com>: > (Just a quick share from work before that neuron goes back to sleep and I > forget it...) > > When a number of domain substitute classes need to satisfy the same tests, > its useful to define these in a superclass and have subclasses define > which domain class is being tested e.g. > TestDelaySemaphoreSchedulerMmicrosecondTeicker>>classForScheduler. > > From the Browser "all tests" can be run for each subclass by clicking the > class's test-icon, > but when that goes red, its not visible which individual test failed, and > you can't run an individual test from the Browser. > > In the same way that extension methods are shown in gray, it would be > useful > for inherited tests to be shown in gray, so each has an individual > indication and can be run separately. > > cheers -ben >

May 29, 2019

Re: [Pharo-dev] Versioning with Iceberg

by Ben Coman

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. cheers -ben

May 29, 2019

Re: [Pharo-dev] Versioning with Iceberg

by ducasse

Hello Can you tell us what you are doing? Because if a project loads always the head then iceberg will load it. Or you should specify a specific commit. Stef > On 29 May 2019, at 11:07, 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. > > Shaping

May 29, 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. Shaping

May 29, 2019