On Thu, Sep 2, 2010 at 1:23 PM, Alberto Bacchelli <alberto.bacchelli@usi.ch>wrote:

BTW, last week I wrote a metacello configuration group to load GlorpDBX

...

with the native postgres driver. You can evaluate first:

Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfGlorpDBX'; load.

and then

(ConfigurationOfGlorpDBX project version: '1.2') load: 'All with PostgreSQL native

Hi,

I followed your instructions and I've been able to load GLORP on a Moose Nightly Built image [1].

I run the 844 tests. 839 of them passed (wow), 4 failed and 1 generated an error. These are the problematic ones:

GlorpManyToManyDBTest>>#testReadNodeAndDeleteChildWithSaveAndContinue GlorpRowMapForMementosCollectionTest>>#testRBSmallDictionary GlorpDateTest>>#testDate GlorpObjectMappedToImaginaryTableTest>>#testReadBackEntireExample GlorpUnitOfWorkTest>>#testRollbackOneToManyAfterAdd

Are these tests failing also on other Pharo images (i.e., they are known "problems")?

Yes. And I don't know how to fix them. If anyone can help, excellent.

Do you know the impact of these failures?

No

will GLORP be reliable without them?

I really don't know, but I guess that yes.

Moose developers, would you include GLORP in the images built by hudson?

I don't think this is a good idea. I think Glorp has nothing to do with Moose on most cases. This is one of the reasons of having a conf, that with one line of code you can load it...So it is not so complicated if you need to do it manually on a normal Moose image.

I think 839 passing tests are good enough for the development image.

Ciao, Alberto

[1] http://hudson.moosetechnology.org/job/moose-with-glamour-seaside/ _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev