Thanks Cyril, thanks for pushing. I've only given you permissions to re-run the build, so keep yourself and Vincent all the credit!

> Slightly off-topic, but I'm also wondering why the test scripts
> download the VM again?�� Why not just use the one that is already in
> vmtarget?

Yes, on one side there is what Cyril says, we need to download a new VM on each new slave, because
��- we build the image on a single slave (unix)
��- we then transfer it to different slaves (mac, windows) to run the tests.

This is like that because originally running the bootstrap was about three times as expensive.
Right now we are on 7minutes to create the minimal image and a couple more to load the rest on top of it.

There is another thing also: we always assumed that slaves do not share disk, so either we re-downloaded a new unix vm or we shared it.
Apparently our assumptions weren't right?

On Tue, Jun 19, 2018 at 5:06 PM Cyril Ferlicot D. <cyril.ferlicot@gmail.com> wrote:
On 19/06/2018 17:02, Alistair Grant wrote:
> Hi Cyril,

> Great work!
>

Thank you. Also thanks to Guille, Vincent, Marcus that helped to find
the problem.

> It would be nice if all the temporary files were in a single folder.
> Cleaning the environment then becomes a matter of deleting that one
> folder.�� (At the moment, there is a vm installed in to the root
> directory, a vmtarget directory (I'm guilty here) and
> bootstrap-cache).
>

Maybe yes :)

> Slightly off-topic, but I'm also wondering why the test scripts
> download the VM again?�� Why not just use the one that is already in
> vmtarget?
>

Because it is a vm linux and tests are executed on OSX and Windows too.

>
>
> This definitely helps :-)
>
>
> Thanks,
> Alistair
>


--
Cyril Ferlicot
https://ferlicot.fr



--

������

Guille Polito

Research Engineer

Centre de Recherche en Informatique, Signal et Automatique de Lille

CRIStAL - UMR 9189

French National Center for Scientific Research - http://www.cnrs.fr


Web: http://guillep.github.io

Phone: +33 06 52 70 66 13