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 On Behalf Of Tim
Mackinnon
Sent: 20 October 2019 22:35
To: Any question about pharo
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 On Behalf Of Tim
Mackinnon
Sent: 20 October 2019 22:35
To: Any question about pharo
Hi Todd,
El sáb., 19 oct. 2019 a las 13:11, Todd Blanchard via Pharo-users (<
pharo-users@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.
>
>
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 wrote:
>
>
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:
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 On Behalf Of Sven Van
Caekenberghe
Sent: 20 October 2019 17:31
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 wrote:
>
> Hello all
>
> I have done some experiments, and
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
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
Hello all
I would be grateful for hints on strategy in investigating test failures on
upgrade. It is an area in which I have no experience; I can see some brute
force approaches, but I suspect there are cleverer ways to do it.
I have OmniBase working successfully on Moose Suite 6.1 (Pharo
On 20 October 2019 at 09.11.06, Pierce Ng (pie...@samadhiweb.com) wrote:
On Sat, Oct 19, 2019 at 04:39:21AM -0700, Kasper Østerbye wrote:
> I am currently working on a github markdown -> pillar tree (the internal
> rep of pillar). I estimate I am a few days out from that one.
Are you doing this
Hi, I'm going systematically through all Glorp tests with PharoADO on SQL
Server and Oracle. The majority is green, but here's the current list of
reds, FYI:
GlorpCacheTest
GlorpTimedExpiryCacheTest
GlorpTimedStrongCacheTest
GlorpDictionaryMappingErrorTest
GlorpDictionaryMappingTest
On Sat, Oct 19, 2019 at 04:39:21AM -0700, Kasper Østerbye wrote:
> I am currently working on a github markdown -> pillar tree (the internal
> rep of pillar). I estimate I am a few days out from that one.
Are you doing this in pure Pharo?
I have wrapped libhoedown, a Markdown to HTML library.
On Sat, Oct 19, 2019 at 01:26:10AM -0700, Todd Blanchard via Pharo-users wrote:
> I loaded GLORP+P3 without issue.
> Trying to load SQLite3 - it also wants to load GLORP which complains of
> conflict.
Todd, to load SQLite3 only:
Metacello new
repository: 'github://astares/Pharo-UDBC/src';
14 matches
Mail list logo
