[Pharo-dev] poor state of fuel

H. Hirzel hannes.hirzel at gmail.com
Tue Aug 29 17:58:45 EDT 2017


On 8/29/17, Tim Mackinnon <tim at testit.works> wrote:
> As a small data point, a fuel file written out on AWS Lambda Linux (not sure
> what version - I think it's an ubuntu, but they don't really say), is
> readable on OS X 64bit .

By the same image or a different one?

--Hannes

> So it seems like you must have found something unusual.
>
> Tim
>
> Sent from my iPhone
>
>> On 29 Aug 2017, at 11:13, Max Leske <maxleske at gmail.com> wrote:
>>
>> Hi Norbert,
>>
>> We still maintain Fuel.
>>
>> I was not aware of the problem you describe. Could you open an issue on
>> github (https://github.com/theseion/Fuel/issues) with a detailed
>> explanation and, if possible, steps to reproduce the problem?
>>
>> Cheers,
>> Max
>>
>>> On 29 August 2017 at 11:04:34, Norbert Hartl (norbert at hartl.name) wrote:
>>>
>>> I'm migrating most of my projects to pharo 6.1 at the moment. I come from
>>> pharo 4, I skipped pharo 5. I use 64 bit which removes a lot of stuff
>>> that does not need to be installed and makes deployment better. That
>>> really feels much better.
>>>
>>> I use jenkins and there if a test fails a fuel dump is written to disk.
>>> The jenkins server is ubuntu linux with the vm of the opensuse build. My
>>> laptop has Mac OS and cannot read back those fuel dumps. I use the same
>>> image version on jenkins and my laptop. Both are 64bit.
>>>
>>> I asked that on discord and there was a mentioning that not only the 64
>>> bit fuel has problems. So I wanted to ask what is the state of fuel right
>>> now. I consider fuel one of the core technologies in pharo and it is sad
>>> if it just stops working.
>>>
>>> Any feedback is highly appreciated,
>>>
>>> Norbert
>>>
>



More information about the Pharo-dev mailing list