[Moose-dev] Re: Issue 736 in moose-technology: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:)

Hi, I looked into this further and I think the issue is that the LAN fixture is not correct. For example, LANNode is supposed to have a LANEditor pool variable, and a accessPoolVariable method, but neither of these are around. I guess you forgot to publish the Moose-TestResources-LAN package :). Cheers, Doru On 16 Dec 2011, at 20:43, Tudor Girba wrote: > Stef, > > Could you take a look for 5 minutes at this one? > > The build is yellow, and I do not know what to do about it. > > Cheers, > Doru > > > On 16 Dec 2011, at 00:57, moose-technology(a)googlecode.com wrote: > >> Updates: >> Owner: stephane...(a)gmail.com >> Labels: Component-SmalltalkImporter Milestone-4.6 >> >> Comment #10 on issue 736 by tudor.gi...(a)gmail.com: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:) >> http://code.google.com/p/moose-technology/issues/detail?id=736 >> >> Stef, some tests are red and the errors are related to parsing pool variables: >> http://ci.moosetechnology.org/job/moose-latest-dev/lastCompletedBuild/tes... >> >> Is it possible that the Pharo patch is still missing? Should I update the base Pharo image? >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > www.tudorgirba.com > > "No matter how many recipes we know, we still value a chef." > > > > > > -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it."