| commit | 40309abb65bed0f14dbb734bee3532664edfd1e6 | |
| author | Cleber Rosa <crosa@redhat.com> | |
| Thu, 13 Jun 2019 13:07:17 +0000 (13 09:07 -0400) | ||
| committer | Alex Bennée <alex.bennee@linaro.org> | |
| Thu, 4 Jul 2019 18:22:58 +0000 (4 19:22 +0100) | ||
| tree | 6ed4be65b44f6004461c683610c24086c77b769c | treesnapshot (tar.gz zip) |
| parent | fcd2060e8efff83b7bdef04323077f87e011fdc4 | commitdiff |
tests/vm: pin ubuntu.i386 image
It's a good practice to always have the same components used in tests.
According to:
https://cloud-images.ubuntu.com/releases/16.04/
New images are released from time to time, and the "release/"
directory points to the latest release. Let's pin to the latest
available version, and while at it, set a hash for verification.
Signed-off-by: Cleber Rosa <crosa@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20190613130718.3763-4-crosa@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
It's a good practice to always have the same components used in tests.
According to:
https://cloud-images.ubuntu.com/releases/16.04/
New images are released from time to time, and the "release/"
directory points to the latest release. Let's pin to the latest
available version, and while at it, set a hash for verification.
Signed-off-by: Cleber Rosa <crosa@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20190613130718.3763-4-crosa@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
| tests/vm/ubuntu.i386 | diffblobblamehistory |