Re: [RFC PATCH] travis.yml: Drop the default softmmu builds

[Thomas Huth <thuth@redhat.com>]

On 16/09/2020 15.22, Alex Bennée wrote:
> 
> Thomas Huth <thuth@redhat.com> writes:
> 
>> On 05/09/2020 14.15, Thomas Huth wrote:
>>> On 05/08/2020 20.54, Thomas Huth wrote:
>>>> The total runtime of all Travis jobs is very long and we are testing
>>>> all softmmu targets in the gitlab-CI already - so we can speed up the
>>>> Travis testing a little bit by not testing the softmmu targets here
>>>> anymore.
>>>>
>>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>>> ---
>>>>  Well, ok, we do not test all the softmmu targets on gitlab-CI with
>>>>  that same ancient version of Ubuntu ... but do we still care about
>>>>  testing all softmmut targets on Ubuntu Xenial at all? ... at least
>>>>  according to our support policy, we do not care about Xenial anymore.
>>>>
>>>>  .travis.yml | 14 --------------
>>>>  1 file changed, 14 deletions(-)
>>>>
>>>> diff --git a/.travis.yml b/.travis.yml
>>>> index 6695c0620f..18290bc51d 100644
>>>> --- a/.travis.yml
>>>> +++ b/.travis.yml
>>>> @@ -123,20 +123,6 @@ jobs:
>>>>          - CONFIG="--disable-system --static"
>>>>          - CACHE_NAME="${TRAVIS_BRANCH}-linux-gcc-default"
>>>>  
>>>> -
>>>> -    # we split the system builds as it takes a while to build them all
>>>> -    - name: "GCC (main-softmmu)"
>>>> -      env:
>>>> -        - CONFIG="--disable-user --target-list=${MAIN_SOFTMMU_TARGETS}"
>>>> -        - CACHE_NAME="${TRAVIS_BRANCH}-linux-gcc-default"
>>>> -
>>>> -
>>>> -    - name: "GCC (other-softmmu)"
>>>> -      env:
>>>> -       - CONFIG="--disable-user --target-list-exclude=${MAIN_SOFTMMU_TARGETS}"
>>>> -        - CACHE_NAME="${TRAVIS_BRANCH}-linux-gcc-default"
>>>> -
>>>> -
>>>>      # Just build tools and run minimal unit and softfloat checks
>>>>      - name: "GCC check-softfloat (user)"
>>>>        env:
>>>>
>>>
>>> Ping?
>>
>> Ping^2 ... Alex, Philippe, any opinions on this patch?
> 
> I'm agnostic on this. Is it worth slightly reducing our coverage for ~50
> minutes of runtime out of 10 hours? I guess it would be a bit greener.

For the last Travis run that succeeded for me, I've got:

 Ran for 1 hr 48 min 32 sec
 Total time 7 hrs 58 min 6 sec

That means the total run time was less than 2h, it's just the total
summed up time of all jobs that is ~8h.

Since both Gitlab und Cirrus jobs finish within one hour, it would be
very convenient to have Travis also finish within one hour, so once
you've pushed your branches to gitlab and github, you could be sure to
get an answer from these three CI systems within 1 hour.

> Acked-by: Alex Bennée <alex.bennee@linaro.org>

Thanks!

  Thomas