Re: [RFC PATCH-for-5.2] gitlab-ci: Do not automatically run Avocado integration tests anymore

[Wainer dos Santos Moschetta <wainersm@redhat.com>]

On 11/27/20 3:29 PM, Thomas Huth wrote:
> On 27/11/2020 18.57, Philippe Mathieu-Daudé wrote:
>> On 11/27/20 6:47 PM, Thomas Huth wrote:
>>> On 27/11/2020 18.41, Philippe Mathieu-Daudé wrote:
>>>> We lately realized that the Avocado framework was not designed
>>>> to be regularly run on CI environments. Therefore, as of 5.2
>>>> we deprecate the gitlab-ci jobs using Avocado. To not disrupt
>>>> current users, it is possible to keep the current behavior by
>>>> setting the QEMU_CI_INTEGRATION_JOBS_PRE_5_2_RELEASE variable
>>>> (see [*]).
>>>>  From now on, using these jobs (or adding new tests to them)
>>>> is strongly discouraged.
>>>>
>>>> Tests based on Avocado will be ported to new job schemes during
>>>> the next releases, with better documentation and templates.
>>> Why should we disable the jobs by default as long as there is no replacement
>>> available yet?
>> Why keep it enabled if it is failing randomly
> We can still disable single jobs if they are not stable, but that's no
> reason to disable all of them by default, is it?
>
>> if images hardcoded
>> in tests are being removed from public servers, etc...?
> That's independent from Avocado, you'll always have that problem if you want
> to test with external images, unless you mirror them into a repository on
> the same server (ie. gitlab), which, however, might not always be possible...

Phil,

on commit 89e076f37d0020bfadb you changed fetch_asset to cancel the test 
if it cannot download a file. Is there anything else that could be done 
to mitigate that problem until we don't have a repository mirror for the 
files?

- Wainer