October 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [ANN] HeySql v1.1

by phil＠highoctane.be

Looks interesting. I'll give it a shot. Same feel about ORMs in general here, so, let's see how it goes. Phil On Sat, Oct 19, 2019 at 6:58 PM Petter <petter.egesund(a)gmail.com> wrote: > Hi, I have just released HeySql, version 1.1 - a database orm for > Postgresql. > > - Support for migrations > - Generation of migration templates based on classes > - Models can now be subclassed > - Updated license to MIT > - Updated docs > - Some minor stuff > > https://github.com/pegesund/heysql > > Petter > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Oct. 21, 2019

Re: [Pharo-users] Strategy for investigating test failures

by PBKResearch

Tim: No, on P6 the test took 11-12 seconds (judged on my ability to count seconds) and the same on P7. Presumably P6 did not have a limit, or it was over 10s. Peter -----Original Message----- From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Tim Mackinnon Sent: 20 October 2019 22:35 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] Strategy for investigating test failures Confusion of failing test aside - is this something that got worse in Pharo 7? Did these tests pass in under 10s in 6 and take longer in 7? This would be a concrete thing to address, and something to check in 8. Tim Sent from my iPhone > On 20 Oct 2019, at 20:11, PBKResearch <peter(a)pbkresearch.co.uk> wrote: > > Sven > > Thanks - the real problem is my unfamiliarity with P7, so hints like this are helpful. I am happier with familiar systems, but I will switch to the latest Moose suite soon. > > Peter > > -----Original Message----- > From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Sven Van Caekenberghe > Sent: 20 October 2019 17:31 > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] Strategy for investigating test failures > > Peter, > > You can override #defaultTimeLimit on the class side of the offending test. > > Yes, this can be confusing. > > There is a new test runner under development, DrTest, in Pharo 8. > > Sven > >> On 20 Oct 2019, at 16:37, PBKResearch <peter(a)pbkresearch.co.uk> wrote: >> >> Hello all >> >> I have done some experiments, and basically all the questions in my previous mail can be ignored. I think it is all a question of timing, which I sort of understand. Perhaps someone can clarify for me. >> >> All my previous tests involved running the whole test suite, to ensure the set-up and tear-down methods were run. As an experiment, I selected the one red method and clicked âRun Testsâ. After about 10 seconds, a halt appeared with the message âTest took too longâ. When I clicked âProceedâ, the green appeared almost immediately. I tried again several times with similar results, although the halt occurred at different places in the code. I went back to my old P6 version and tried running tests on the one method; each time, it ran to green in about 11-12 seconds. >> >> So back now to the P7 version; wondered if there is now a setting for permitted test duration. Eventually found it under âSystemâ, default 10 secs. Changed to 15 secs, re-run red test, now comes up green. Re-run whole test suite, all green. >> >> So it all comes down to my ignorance of test settings. But Pharo is less than helpful; if you run the whole test suite, there is no way to distinguish a test which failed due to a wrong assertion from one which was terminated for taking too long â or did I miss something? >> >> Peter Kenny > > >

Oct. 20, 2019

Re: [Pharo-users] Strategy for investigating test failures

by PBKResearch

Tim: No, on P6 the test took 11-12 seconds (judged on my ability to count seconds) and the same on P7. Presumably P6 did not have a limit, or it was over 10s. Peter -----Original Message----- From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Tim Mackinnon Sent: 20 October 2019 22:35 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] Strategy for investigating test failures Confusion of failing test aside - is this something that got worse in Pharo 7? Did these tests pass in under 10s in 6 and take longer in 7? This would be a concrete thing to address, and something to check in 8. Tim Sent from my iPhone > On 20 Oct 2019, at 20:11, PBKResearch <peter(a)pbkresearch.co.uk> wrote: > > Sven > > Thanks - the real problem is my unfamiliarity with P7, so hints like this are helpful. I am happier with familiar systems, but I will switch to the latest Moose suite soon. > > Peter > > -----Original Message----- > From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Sven Van Caekenberghe > Sent: 20 October 2019 17:31 > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] Strategy for investigating test failures > > Peter, > > You can override #defaultTimeLimit on the class side of the offending test. > > Yes, this can be confusing. > > There is a new test runner under development, DrTest, in Pharo 8. > > Sven > >> On 20 Oct 2019, at 16:37, PBKResearch <peter(a)pbkresearch.co.uk> wrote: >> >> Hello all >> >> I have done some experiments, and basically all the questions in my previous mail can be ignored. I think it is all a question of timing, which I sort of understand. Perhaps someone can clarify for me. >> >> All my previous tests involved running the whole test suite, to ensure the set-up and tear-down methods were run. As an experiment, I selected the one red method and clicked âRun Testsâ. After about 10 seconds, a halt appeared with the message âTest took too longâ. When I clicked âProceedâ, the green appeared almost immediately. I tried again several times with similar results, although the halt occurred at different places in the code. I went back to my old P6 version and tried running tests on the one method; each time, it ran to green in about 11-12 seconds. >> >> So back now to the P7 version; wondered if there is now a setting for permitted test duration. Eventually found it under âSystemâ, default 10 secs. Changed to 15 secs, re-run red test, now comes up green. Re-run whole test suite, all green. >> >> So it all comes down to my ignorance of test settings. But Pharo is less than helpful; if you run the whole test suite, there is no way to distinguish a test which failed due to a wrong assertion from one which was terminated for taking too long â or did I miss something? >> >> Peter Kenny > > >

Oct. 20, 2019

Re: [Pharo-users] Glorp + P3 + SQLite

by HernÃ¡n Morales Durand

Hi Todd, El sÃ¡b., 19 oct. 2019 a las 13:11, Todd Blanchard via Pharo-users (< pharo-users(a)lists.pharo.org>) escribiÃ³: > I should probably mention that I do not really have a great handle on how > package configurations work these days. > > Coming back to Smalltalk after a long time away. > > Welcome back! > Pointer to an explanation of how package configurations work would be > great. > > Have a look at: https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… Cheers, HernÃ¡n

Oct. 20, 2019

Re: [Pharo-users] Strategy for investigating test failures

by Tim Mackinnon

Confusion of failing test aside - is this something that got worse in Pharo 7? Did these tests pass in under 10s in 6 and take longer in 7? This would be a concrete thing to address, and something to check in 8. Tim Sent from my iPhone > On 20 Oct 2019, at 20:11, PBKResearch <peter(a)pbkresearch.co.uk> wrote: > > Sven > > Thanks - the real problem is my unfamiliarity with P7, so hints like this are helpful. I am happier with familiar systems, but I will switch to the latest Moose suite soon. > > Peter > > -----Original Message----- > From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Sven Van Caekenberghe > Sent: 20 October 2019 17:31 > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] Strategy for investigating test failures > > Peter, > > You can override #defaultTimeLimit on the class side of the offending test. > > Yes, this can be confusing. > > There is a new test runner under development, DrTest, in Pharo 8. > > Sven > >> On 20 Oct 2019, at 16:37, PBKResearch <peter(a)pbkresearch.co.uk> wrote: >> >> Hello all >> >> I have done some experiments, and basically all the questions in my previous mail can be ignored. I think it is all a question of timing, which I sort of understand. Perhaps someone can clarify for me. >> >> All my previous tests involved running the whole test suite, to ensure the set-up and tear-down methods were run. As an experiment, I selected the one red method and clicked âRun Testsâ. After about 10 seconds, a halt appeared with the message âTest took too longâ. When I clicked âProceedâ, the green appeared almost immediately. I tried again several times with similar results, although the halt occurred at different places in the code. I went back to my old P6 version and tried running tests on the one method; each time, it ran to green in about 11-12 seconds. >> >> So back now to the P7 version; wondered if there is now a setting for permitted test duration. Eventually found it under âSystemâ, default 10 secs. Changed to 15 secs, re-run red test, now comes up green. Re-run whole test suite, all green. >> >> So it all comes down to my ignorance of test settings. But Pharo is less than helpful; if you run the whole test suite, there is no way to distinguish a test which failed due to a wrong assertion from one which was terminated for taking too long â or did I miss something? >> >> Peter Kenny > > >

Oct. 20, 2019

Re: [Pharo-users] PharoADO

by eftomi

It was not so bad as it looked - all tests under Glorp-Tests-Tests are now green for Oracle and SQL Server. There are some reds under Database and DatabaseTypes, but they seem manageable to resolve. I hope I can publish a first reliable release soon :-) Best wishes, Tomaz -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 20, 2019

Re: [Pharo-users] Strategy for investigating test failures

by PBKResearch

Sven Thanks - the real problem is my unfamiliarity with P7, so hints like this are helpful. I am happier with familiar systems, but I will switch to the latest Moose suite soon. Peter -----Original Message----- From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Sven Van Caekenberghe Sent: 20 October 2019 17:31 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] Strategy for investigating test failures Peter, You can override #defaultTimeLimit on the class side of the offending test. Yes, this can be confusing. There is a new test runner under development, DrTest, in Pharo 8. Sven > On 20 Oct 2019, at 16:37, PBKResearch <peter(a)pbkresearch.co.uk> wrote: > > Hello all > > I have done some experiments, and basically all the questions in my previous mail can be ignored. I think it is all a question of timing, which I sort of understand. Perhaps someone can clarify for me. > > All my previous tests involved running the whole test suite, to ensure the set-up and tear-down methods were run. As an experiment, I selected the one red method and clicked âRun Testsâ. After about 10 seconds, a halt appeared with the message âTest took too longâ. When I clicked âProceedâ, the green appeared almost immediately. I tried again several times with similar results, although the halt occurred at different places in the code. I went back to my old P6 version and tried running tests on the one method; each time, it ran to green in about 11-12 seconds. > > So back now to the P7 version; wondered if there is now a setting for permitted test duration. Eventually found it under âSystemâ, default 10 secs. Changed to 15 secs, re-run red test, now comes up green. Re-run whole test suite, all green. > > So it all comes down to my ignorance of test settings. But Pharo is less than helpful; if you run the whole test suite, there is no way to distinguish a test which failed due to a wrong assertion from one which was terminated for taking too long â or did I miss something? > > Peter Kenny

Oct. 20, 2019

Re: [Pharo-users] Strategy for investigating test failures

by Sven Van Caekenberghe

Peter, You can override #defaultTimeLimit on the class side of the offending test. Yes, this can be confusing. There is a new test runner under development, DrTest, in Pharo 8. Sven > On 20 Oct 2019, at 16:37, PBKResearch <peter(a)pbkresearch.co.uk> wrote: > > Hello all > > I have done some experiments, and basically all the questions in my previous mail can be ignored. I think it is all a question of timing, which I sort of understand. Perhaps someone can clarify for me. > > All my previous tests involved running the whole test suite, to ensure the set-up and tear-down methods were run. As an experiment, I selected the one red method and clicked âRun Testsâ. After about 10 seconds, a halt appeared with the message âTest took too longâ. When I clicked âProceedâ, the green appeared almost immediately. I tried again several times with similar results, although the halt occurred at different places in the code. I went back to my old P6 version and tried running tests on the one method; each time, it ran to green in about 11-12 seconds. > > So back now to the P7 version; wondered if there is now a setting for permitted test duration. Eventually found it under âSystemâ, default 10 secs. Changed to 15 secs, re-run red test, now comes up green. Re-run whole test suite, all green. > > So it all comes down to my ignorance of test settings. But Pharo is less than helpful; if you run the whole test suite, there is no way to distinguish a test which failed due to a wrong assertion from one which was terminated for taking too long â or did I miss something? > > Peter Kenny

Oct. 20, 2019

ESUG Videos

by Norbert Hartl

It has been a while since ESUG took place in cologne. We are sorry for the delay in providing the videos of the talks but the end of summer was a busy time for the guy doing the videos and there is quite some material to post-process. Talk videos are prepared now and we start soon to upload them to the github channel at [1]. Additional to the talks we ordered a short image video for the conference so people get an impression what the event is like. As a teaser before the uploading starts we want to make the image video available to you https://zweidenker.de/en/esug-conference-2019/ <https://zweidenker.de/en/esug-conference-2019/> As soon as there are videos available Marcus will drop a note about it. Hope you like it! the ZWEIDENKER Team [1] https://www.youtube.com/channel/UCO-vBhaKVZf0al-ISMMPvRw <https://www.youtube.com/channel/UCO-vBhaKVZf0al-ISMMPvRw>

Oct. 20, 2019

Strategy for investigating test failures

by PBKResearch

Hello all I have done some experiments, and basically all the questions in my previous mail can be ignored. I think it is all a question of timing, which I sort of understand. Perhaps someone can clarify for me. All my previous tests involved running the whole test suite, to ensure the set-up and tear-down methods were run. As an experiment, I selected the one red method and clicked 'Run Tests'. After about 10 seconds, a halt appeared with the message 'Test took too long'. When I clicked 'Proceed', the green appeared almost immediately. I tried again several times with similar results, although the halt occurred at different places in the code. I went back to my old P6 version and tried running tests on the one method; each time, it ran to green in about 11-12 seconds. So back now to the P7 version; wondered if there is now a setting for permitted test duration. Eventually found it under 'System', default 10 secs. Changed to 15 secs, re-run red test, now comes up green. Re-run whole test suite, all green. So it all comes down to my ignorance of test settings. But Pharo is less than helpful; if you run the whole test suite, there is no way to distinguish a test which failed due to a wrong assertion from one which was terminated for taking too long - or did I miss something? Peter Kenny

Oct. 20, 2019