Yeh, to be more precise,
* the problem is that the image somehow got it's display size modified to a
very small one.
* And that happenned while building an image in the CI in headless mode.
* If the same image is built locally in a vm launched in non-headless mode,
the issue cannot be reproduced.
guillermo was suspecting a problem with the interpretatin of the image
metadata
Maybe related?
http://forum.world.st/BUG-A-problem-with-callbacks-that-shows-up-in-64bits-but-is-on-32bits-too-td4938152.html
On Sat, Mar 11, 2017 at 2:22 AM, Cyril Ferlicot
wrote:
On
Maybe related?
http://forum.world.st/BUG-A-problem-with-callbacks-that-shows-up-in-64bits-but-is-on-32bits-too-td4938152.html
On Sat, Mar 11, 2017 at 2:22 AM, Cyril Ferlicot
wrote:
>
> On ven. 10 mars 2017 at 18:42, stepharong wrote:
>>
>> We found
On ven. 10 mars 2017 at 18:42, stepharong wrote:
> We found the problem with Guillermo and this may be a problem of the last
> VM.
>
> The image got its starting window size really small: some pixels on some
> pixles.
> So may be the metadata of the image are systematically
We found the problem with Guillermo and this may be a problem of the last
VM.
The image got its starting window size really small: some pixels on some
pixles.
So may be the metadata of the image are systematically corrupted.
Hi
I have a jenkins that produce an image that does not start
On 10/03/2017 15:27, Stephane Ducasse wrote:
> Hi
>
> I have a jenkins that produce an image that does not start
> when I try to open it locally.
>
> Now if I take the image and load the "same" configuration I get a
> working image
>
> I have not idea how to debug that.
>
> Stef
Hi,
I have
Hi
I have a jenkins that produce an image that does not start
when I try to open it locally.
Now if I take the image and load the "same" configuration I get a working
image
I have not idea how to debug that.
Stef