OSProcess vs ImageSaving

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

OSProcess vs ImageSaving

Camillo Bruni

I discovered a weird bug on OSX (10.7.1) with the latest builds from jenkins for both Cog and Stack:

When opening the image from the command-line image saving does

- not work in the Blessed VM ('Croquet Closure Stack VM [StackInterpreter VMMaker-oscog-EstebanLorenzano.109] 21.0 ')

- works in the dev / non-blessed version ('Croquet Closure Stack VM [StackInterpreter VMMaker-oscog-IgorStasenko.123] 21.0 Commit: fe0330a267e1a99bd27bd161443c5cc255fde8c3')

It both works when I open the image with the UI (drag n drop onto the VM).
I tried different variants of `open` resulting in the same behavior.

Any clue on how to deal with that?

The simplest solution would be to use the non-blessed VM but that one does not support OSProcess yet, which is a requirement for my project.

best cami
Reply | Threaded
Open this post in threaded view
|

Re: OSProcess vs ImageSaving

EstebanLM

image saving? just "save image" from the menu? is that what is not working?


El 03/10/2011, a las 1:34p.m., Camillo Bruni escribió:

>
> I discovered a weird bug on OSX (10.7.1) with the latest builds from jenkins for both Cog and Stack:
>
> When opening the image from the command-line image saving does
>
> - not work in the Blessed VM ('Croquet Closure Stack VM [StackInterpreter VMMaker-oscog-EstebanLorenzano.109] 21.0 ')
>
> - works in the dev / non-blessed version ('Croquet Closure Stack VM [StackInterpreter VMMaker-oscog-IgorStasenko.123] 21.0 Commit: fe0330a267e1a99bd27bd161443c5cc255fde8c3')
>
> It both works when I open the image with the UI (drag n drop onto the VM).
> I tried different variants of `open` resulting in the same behavior.
>
> Any clue on how to deal with that?
>
> The simplest solution would be to use the non-blessed VM but that one does not support OSProcess yet, which is a requirement for my project.
>
> best cami

Reply | Threaded
Open this post in threaded view
|

Re: OSProcess vs ImageSaving

EstebanLM
In reply to this post by Camillo Bruni

ha... it's true! (and really weird)
working on that now :)

El 03/10/2011, a las 1:34p.m., Camillo Bruni escribió:

>
> I discovered a weird bug on OSX (10.7.1) with the latest builds from jenkins for both Cog and Stack:
>
> When opening the image from the command-line image saving does
>
> - not work in the Blessed VM ('Croquet Closure Stack VM [StackInterpreter VMMaker-oscog-EstebanLorenzano.109] 21.0 ')
>
> - works in the dev / non-blessed version ('Croquet Closure Stack VM [StackInterpreter VMMaker-oscog-IgorStasenko.123] 21.0 Commit: fe0330a267e1a99bd27bd161443c5cc255fde8c3')
>
> It both works when I open the image with the UI (drag n drop onto the VM).
> I tried different variants of `open` resulting in the same behavior.
>
> Any clue on how to deal with that?
>
> The simplest solution would be to use the non-blessed VM but that one does not support OSProcess yet, which is a requirement for my project.
>
> best cami

Reply | Threaded
Open this post in threaded view
|

Re: OSProcess vs ImageSaving

Camillo Bruni
In reply to this post by EstebanLM

        Smalltalk snapshot: true andQuit: true.

Does not alter the image file e.g. the image is not saved

cami


On 2011-10-03, at 18:39, Esteban Lorenzano wrote:

>
> image saving? just "save image" from the menu? is that what is not working?
>
>
> El 03/10/2011, a las 1:34p.m., Camillo Bruni escribió:
>
>>
>> I discovered a weird bug on OSX (10.7.1) with the latest builds from jenkins for both Cog and Stack:
>>
>> When opening the image from the command-line image saving does
>>
>> - not work in the Blessed VM ('Croquet Closure Stack VM [StackInterpreter VMMaker-oscog-EstebanLorenzano.109] 21.0 ')
>>
>> - works in the dev / non-blessed version ('Croquet Closure Stack VM [StackInterpreter VMMaker-oscog-IgorStasenko.123] 21.0 Commit: fe0330a267e1a99bd27bd161443c5cc255fde8c3')
>>
>> It both works when I open the image with the UI (drag n drop onto the VM).
>> I tried different variants of `open` resulting in the same behavior.
>>
>> Any clue on how to deal with that?
>>
>> The simplest solution would be to use the non-blessed VM but that one does not support OSProcess yet, which is a requirement for my project.
>>
>> best cami
>

Reply | Threaded
Open this post in threaded view
|

Re: OSProcess vs ImageSaving

Camillo Bruni
In reply to this post by EstebanLM

thanks :)

On 2011-10-03, at 18:42, Esteban Lorenzano wrote:

> ha... it's true! (and really weird)
> working on that now :)
>
> El 03/10/2011, a las 1:34p.m., Camillo Bruni escribió:
>> I discovered a weird bug on OSX (10.7.1) with the latest builds from jenkins for both Cog and Stack:
>>
>> When opening the image from the command-line image saving does
>>
>> - not work in the Blessed VM ('Croquet Closure Stack VM [StackInterpreter VMMaker-oscog-EstebanLorenzano.109] 21.0 ')
>>
>> - works in the dev / non-blessed version ('Croquet Closure Stack VM [StackInterpreter VMMaker-oscog-IgorStasenko.123] 21.0 Commit: fe0330a267e1a99bd27bd161443c5cc255fde8c3')
>>
>> It both works when I open the image with the UI (drag n drop onto the VM).
>> I tried different variants of `open` resulting in the same behavior.
>>
>> Any clue on how to deal with that?
>>
>> The simplest solution would be to use the non-blessed VM but that one does not support OSProcess yet, which is a requirement for my project.
>>
>> best cami
>

Reply | Threaded
Open this post in threaded view
|

Re: OSProcess vs ImageSaving

EstebanLM

Hi,
I uploaded a fix, but jenkins is taking ages to build.
I think it is stuck... if someone can take a look...

El 03/10/2011, a las 1:44p.m., Camillo Bruni escribió:

>
> thanks :)
>
> On 2011-10-03, at 18:42, Esteban Lorenzano wrote:
>> ha... it's true! (and really weird)
>> working on that now :)
>>
>> El 03/10/2011, a las 1:34p.m., Camillo Bruni escribió:
>>> I discovered a weird bug on OSX (10.7.1) with the latest builds from jenkins for both Cog and Stack:
>>>
>>> When opening the image from the command-line image saving does
>>>
>>> - not work in the Blessed VM ('Croquet Closure Stack VM [StackInterpreter VMMaker-oscog-EstebanLorenzano.109] 21.0 ')
>>>
>>> - works in the dev / non-blessed version ('Croquet Closure Stack VM [StackInterpreter VMMaker-oscog-IgorStasenko.123] 21.0 Commit: fe0330a267e1a99bd27bd161443c5cc255fde8c3')
>>>
>>> It both works when I open the image with the UI (drag n drop onto the VM).
>>> I tried different variants of `open` resulting in the same behavior.
>>>
>>> Any clue on how to deal with that?
>>>
>>> The simplest solution would be to use the non-blessed VM but that one does not support OSProcess yet, which is a requirement for my project.
>>>
>>> best cami
>>
>

Reply | Threaded
Open this post in threaded view
|

Re: OSProcess vs ImageSaving

Camillo Bruni

killed the build let's see if it works now..

On 2011-10-03, at 23:33, Esteban Lorenzano wrote:

> Hi,
> I uploaded a fix, but jenkins is taking ages to build.
> I think it is stuck... if someone can take a look...
>
> El 03/10/2011, a las 1:44p.m., Camillo Bruni escribió:
>
>>
>> thanks :)
>>
>> On 2011-10-03, at 18:42, Esteban Lorenzano wrote:
>>> ha... it's true! (and really weird)
>>> working on that now :)
>>>
>>> El 03/10/2011, a las 1:34p.m., Camillo Bruni escribió:
>>>> I discovered a weird bug on OSX (10.7.1) with the latest builds from jenkins for both Cog and Stack:
>>>>
>>>> When opening the image from the command-line image saving does
>>>>
>>>> - not work in the Blessed VM ('Croquet Closure Stack VM [StackInterpreter VMMaker-oscog-EstebanLorenzano.109] 21.0 ')
>>>>
>>>> - works in the dev / non-blessed version ('Croquet Closure Stack VM [StackInterpreter VMMaker-oscog-IgorStasenko.123] 21.0 Commit: fe0330a267e1a99bd27bd161443c5cc255fde8c3')
>>>>
>>>> It both works when I open the image with the UI (drag n drop onto the VM).
>>>> I tried different variants of `open` resulting in the same behavior.
>>>>
>>>> Any clue on how to deal with that?
>>>>
>>>> The simplest solution would be to use the non-blessed VM but that one does not support OSProcess yet, which is a requirement for my project.
>>>>
>>>> best cami
>>>
>>
>