Comment #5 on issue 736 by tudor.gi...@gmail.com: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:) http://code.google.com/p/moose-technology/issues/detail?id=736

Please provide a full script that can be easily reproduced.

Comment #7 on issue 736 by stephane...@gmail.com: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:) http://code.google.com/p/moose-technology/issues/detail?id=736

I'm checking it now and I think that this is related to a bug in pharo 1.3 (related to Pool variable look up). I will check if I load the fix if it solves the problem.

Comment #9 on issue 736 by stephane...@gmail.com: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:) http://code.google.com/p/moose-technology/issues/detail?id=736

I checked and loading 4899 does not help but the problem is really linked with the use of Pool Variable. I will have a look.

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@googlecode.com wrote:

Updates: Owner: stephane...@gmail.com Labels: Component-SmalltalkImporter Milestone-4.6

Comment #10 on issue 736 by tudor.gi...@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/testRe...

Is it possible that the Pharo patch is still missing? Should I update the base Pharo image?

---

Moose-dev mailing list Moose-dev@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."

Hi doru

I was more than busy. I published the missing package. I hope it will be ok.

Stef

On Dec 16, 2011, at 11:17 PM, Tudor Girba wrote:

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@googlecode.com wrote:

...

Updates: Owner: stephane...@gmail.com Labels: Component-SmalltalkImporter Milestone-4.6

Comment #10 on issue 736 by tudor.gi...@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/testRe...

Is it possible that the Pharo patch is still missing? Should I update the base Pharo image?

---

Moose-dev mailing list Moose-dev@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."

They will get green as soon as squeaksource gets back online :).

Doru

On 17 Dec 2011, at 16:07, Alexandre Bergel wrote:

Next week I will have more time to devote to moose. I would like to have all the tests green.

Cheers, Alexandre

On 16 Dec 2011, at 16: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@googlecode.com wrote:

...

Updates: Owner: stephane...@gmail.com Labels: Component-SmalltalkImporter Milestone-4.6

Comment #10 on issue 736 by tudor.gi...@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/testRe...

Is it possible that the Pharo patch is still missing? Should I update the base Pharo image?

---

Moose-dev mailing list Moose-dev@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."

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com

"It's not how it is, it is how we see it."

Comment #12 on issue 736 by usman.bh...@gmail.com: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:) http://code.google.com/p/moose-technology/issues/detail?id=736

The problem seems to be resolved now. The import of Citezen (all packages) now works in Moose.