Re: [PATCH 1/1] tests/acceptance: change armbian archive to a faster host

[Cleber Rosa <crosa@redhat.com>]

[-- Attachment #1: Type: text/plain, Size: 2308 bytes --]

On Wed, May 26, 2021 at 05:56:01PM -0300, Willian Rampazzo wrote:
> The current host for the image
> Armbian_20.08.1_Orangepipc_bionic_current_5.8.5.img.xz
> (archive.armbian.com) is extremely slow in the last couple of weeks,
> making the job running the test
> tests/system/boot_linux_console.py:BootLinuxConsole.test_arm_orangepi_bionic_20_08
> for the first time when the image is not yet on GitLab cache, time out
> while the image is being downloaded.
> 
> This changes the host to one faster, so new users with an empty cache
> are not impacted.
> 
> Signed-off-by: Willian Rampazzo <willianr@redhat.com>
> ---
>  tests/acceptance/boot_linux_console.py | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/tests/acceptance/boot_linux_console.py b/tests/acceptance/boot_linux_console.py
> index 276a53f146..51c23b822c 100644
> --- a/tests/acceptance/boot_linux_console.py
> +++ b/tests/acceptance/boot_linux_console.py
> @@ -804,7 +804,8 @@ def test_arm_orangepi_bionic_20_08(self):
>          # to 1036 MiB, but the underlying filesystem is 1552 MiB...
>          # As we expand it to 2 GiB we are safe.
>  
> -        image_url = ('https://archive.armbian.com/orangepipc/archive/'
> +        image_url = ('https://armbian.systemonachip.net/'
> +                     'archive/orangepipc/archive/'

Hi Willian,

I was pretty annoyed by my pipeline failures, that I came up with:

   https://gitlab.com/cleber.gnu/qemu/-/commit/917b3e376e682e9c35c6f7f597ffca110c719e13

To prove that it was a GitLab <-> archive.arbian.com issue.  But I
wonder:

 1. how susceptible to the same situation is this other mirror?
 2. how trustworthy is this mirror, say, stability wise? Maybe
    people in the armbian community would have some info?

Depending on the feedback we get about, this can be a very valid
hotfix/workaround indeed.  But the core issues we need to look into
are:

 a. applying a timeout when fetching assets.  If the asset fails to be
    fetched within the timeout, the test simply gets canceled.

 b. evaluate the use of the multiple "locations" support that the
    avocado.utils.asset library has (and improve it if necessary).

Anyway, thanks for looking into this, and let's wait a bit for
feedback.

- Cleber.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]