Hi Cyril & Guille,
On Tue, Jun 19, 2018 at 5:06 PM Cyril Ferlicot D. <cyril.ferlicot@gmail.com> wrote:
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.
On Tue, 19 Jun 2018 at 18:49, Guillermo Polito <guillermopolito@gmail.com> wrote:
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.
Thanks for your explanations, I hadn't considered these requirements. Apart from avoiding duplication and resource waste by re-running the bootstrap, testing a single image does a sanity check that we haven't broken cross-platform compatibility in some way. Thanks again, Alistair
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?