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

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|

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

moose-technology
Updates:
        Summary: Moose crashes when importing Citezen  
(OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:)

Comment #3 on issue 736 by [hidden email]: Moose crashes when  
importing Citezen (OrderedCollection(Object)>>doesNotUnderstand:  
#unsafeAdd:)
http://code.google.com/p/moose-technology/issues/detail?id=736

(No comment was entered for this change.)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

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

moose-technology

Comment #4 on issue 736 by [hidden email]: Moose crashes when  
importing Citezen (OrderedCollection(Object)>>doesNotUnderstand:  
#unsafeAdd:)
http://code.google.com/p/moose-technology/issues/detail?id=736

the package StefScript.
I have the impression that it may be linked with the shared pool used.

Check in the configurationOfCitezen for noweb.



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

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

moose-technology

Comment #5 on issue 736 by [hidden email]: 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.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

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

moose-technology

Comment #6 on issue 736 by [hidden email]: Moose crashes when  
importing Citezen (OrderedCollection(Object)>>doesNotUnderstand:  
#unsafeAdd:)
http://code.google.com/p/moose-technology/issues/detail?id=736

I hope to get some times next week to have a look.
Else this is the citizen-StefScripts that cannot be loaded.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

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

moose-technology

Comment #7 on issue 736 by [hidden email]: 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.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

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

moose-technology

Comment #8 on issue 736 by [hidden email]: Moose crashes when  
importing Citezen (OrderedCollection(Object)>>doesNotUnderstand:  
#unsafeAdd:)
http://code.google.com/p/moose-technology/issues/detail?id=736

Thanks!

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

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

moose-technology

Comment #9 on issue 736 by [hidden email]: 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.



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

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

moose-technology
Updates:
        Owner: [hidden email]
        Labels: Component-SmalltalkImporter Milestone-4.6

Comment #10 on issue 736 by [hidden email]: 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/testReport/

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


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

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

Tudor Girba-2
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, [hidden email] wrote:

> Updates:
> Owner: [hidden email]
> Labels: Component-SmalltalkImporter Milestone-4.6
>
> Comment #10 on issue 736 by [hidden email]: 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/testReport/
>
> Is it possible that the Pharo patch is still missing? Should I update the base Pharo image?
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> 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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

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

Tudor Girba-2
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, [hidden email] wrote:
>
>> Updates:
>> Owner: [hidden email]
>> Labels: Component-SmalltalkImporter Milestone-4.6
>>
>> Comment #10 on issue 736 by [hidden email]: 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/testReport/
>>
>> Is it possible that the Pharo patch is still missing? Should I update the base Pharo image?
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> 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."


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

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

Stéphane Ducasse
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, [hidden email] wrote:
>>
>>> Updates:
>>> Owner: [hidden email]
>>> Labels: Component-SmalltalkImporter Milestone-4.6
>>>
>>> Comment #10 on issue 736 by [hidden email]: 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/testReport/
>>>
>>> Is it possible that the Pharo patch is still missing? Should I update the base Pharo image?
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> 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."
>


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

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

abergel
In reply to this post by Tudor Girba-2
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, [hidden email] wrote:
>
>> Updates:
>> Owner: [hidden email]
>> Labels: Component-SmalltalkImporter Milestone-4.6
>>
>> Comment #10 on issue 736 by [hidden email]: 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/testReport/
>>
>> Is it possible that the Pharo patch is still missing? Should I update the base Pharo image?
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> 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
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

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

Tudor Girba-2
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, [hidden email] wrote:
>>
>>> Updates:
>>> Owner: [hidden email]
>>> Labels: Component-SmalltalkImporter Milestone-4.6
>>>
>>> Comment #10 on issue 736 by [hidden email]: 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/testReport/
>>>
>>> Is it possible that the Pharo patch is still missing? Should I update the base Pharo image?
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> 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
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

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


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

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

moose-technology
In reply to this post by moose-technology
Updates:
        Labels: -Milestone-4.6

Comment #11 on issue 736 by [hidden email]: Moose crashes when  
importing Citezen (OrderedCollection(Object)>>doesNotUnderstand:  
#unsafeAdd:)
http://code.google.com/p/moose-technology/issues/detail?id=736

(No comment was entered for this change.)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

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

moose-technology

Comment #12 on issue 736 by [hidden email]: 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.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

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

moose-technology
Updates:
        Status: Fixed

Comment #13 on issue 736 by [hidden email]: Moose crashes when  
importing Citezen (OrderedCollection(Object)>>doesNotUnderstand:  
#unsafeAdd:)
http://code.google.com/p/moose-technology/issues/detail?id=736

(No comment was entered for this change.)

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev