[PATCH-for-5.2 v4 00/17] ci: Move various jobs from Travis to GitLab CI

Philippe Mathieu-Daudé posted 17 patches 3 years, 5 months ago
Failed in applying to current master (apply log)
configure                                  |   3 +
meson.build                                |   6 +-
hw/i386/acpi-build.c                       |  45 ++--
.gitlab-ci.d/crossbuilds.yml               |   9 +
.gitlab-ci.yml                             | 228 +++++++++++++++++++--
.travis.yml                                |  78 -------
MAINTAINERS                                |   3 +-
scripts/{travis => ci}/coverage-summary.sh |   2 +-
tests/docker/dockerfiles/fedora.docker     |   1 +
9 files changed, 249 insertions(+), 126 deletions(-)
rename scripts/{travis => ci}/coverage-summary.sh (92%)
[PATCH-for-5.2 v4 00/17] ci: Move various jobs from Travis to GitLab CI
Posted by Philippe Mathieu-Daudé 3 years, 5 months ago
We have various job covered on Travis-CI, but recommend the
community to use GitLab, so build failures are missed.

We need help to move the jobs to GitLab (we will keep the s390x
and ppc64 containerized jobs on Travis as there is no similar
offer on GitLab). Start moving jobs.

Resulting pipelines (96 jobs in 71 minutes and 4 seconds)
  https://gitlab.com/philmd/qemu/-/pipelines/213351318
  https://gitlab.com/philmd/qemu/-/pipelines/213378500

Patches 1-3 are included because without them some jobs are
failing; but they will be merged via different trees.

Since v3:
- moving various other jobs
- make some jobs optional

Since v2:
- Run m68k qtests (Thomas)
- Reworded hw/9pfs description (Greg)
- Added tags

Since v1:
- Fix Xen+9pfs config (Paolo)
- Run AVR qtests (Thomas)

Based-on: <20201104115706.3101190-1-philmd@redhat.com>

Philippe Mathieu-Daudé (16):
  configure: Check vhost-user is available to build
    vhost-user-blk-server
  hw/i386/acpi-build: Fix maybe-uninitialized error when ACPI hotplug
    off
  MAINTAINERS: Add gitlab-pipeline-status script to GitLab CI section
  gitlab-ci: Split CONFIGURE_ARGS one argument per line for
    build-disabled
  gitlab-ci: Update 'build-disabled' to cover all configurable options
  gitlab-ci: Move job testing --without-default-devices across to gitlab
  gitlab-ci: Move linux-user debug-tcg test across to gitlab
  gitlab-ci: Move gprof/gcov test across to gitlab
  gitlab-ci: Move user-static test across to gitlab
  gitlab-ci: Move tools-only and softfloat tests across to gitlab
  gitlab-ci: Move coroutine tests across to gitlab
  tests/docker: Install lttng-ust-devel package in Fedora image
  gitlab-ci: Move trace backend tests across to gitlab
  gitlab-ci: Add test for Xen (on CentOS 7)
  gitlab-ci: Make some ARM 32-bit jobs optional
  gitlab-ci: Make MIPS user-mode 32-bit little-endian job optional

Stefan Hajnoczi (1):
  meson: always include contrib/libvhost-user

 configure                                  |   3 +
 meson.build                                |   6 +-
 hw/i386/acpi-build.c                       |  45 ++--
 .gitlab-ci.d/crossbuilds.yml               |   9 +
 .gitlab-ci.yml                             | 228 +++++++++++++++++++--
 .travis.yml                                |  78 -------
 MAINTAINERS                                |   3 +-
 scripts/{travis => ci}/coverage-summary.sh |   2 +-
 tests/docker/dockerfiles/fedora.docker     |   1 +
 9 files changed, 249 insertions(+), 126 deletions(-)
 rename scripts/{travis => ci}/coverage-summary.sh (92%)

-- 
2.26.2


Re: [PATCH-for-5.2 v4 00/17] ci: Move various jobs from Travis to GitLab CI
Posted by Thomas Huth 3 years, 4 months ago
On 08/11/2020 21.45, Philippe Mathieu-Daudé wrote:
> We have various job covered on Travis-CI, but recommend the
> community to use GitLab, so build failures are missed.
> 
> We need help to move the jobs to GitLab (we will keep the s390x
> and ppc64 containerized jobs on Travis as there is no similar
> offer on GitLab). Start moving jobs.

Now that the hard freeze is over, I've put some of your patches (that looked
ready to go) in my current pull request. Once that has been merged, could
you please respin your series with the remaining patches? That would be
great, since Travis is likely unusable for every average developer by the
end of the year...

 Thomas


Re: [PATCH-for-5.2 v4 00/17] ci: Move various jobs from Travis to GitLab CI
Posted by Alex Bennée 3 years, 5 months ago
Philippe Mathieu-Daudé <philmd@redhat.com> writes:

> We have various job covered on Travis-CI, but recommend the
> community to use GitLab, so build failures are missed.
>
> We need help to move the jobs to GitLab (we will keep the s390x
> and ppc64 containerized jobs on Travis as there is no similar
> offer on GitLab). Start moving jobs.
>
> Resulting pipelines (96 jobs in 71 minutes and 4 seconds)
>   https://gitlab.com/philmd/qemu/-/pipelines/213351318
>   https://gitlab.com/philmd/qemu/-/pipelines/213378500
>
> Patches 1-3 are included because without them some jobs are
> failing; but they will be merged via different trees.

Which trees? I'm currently holding 2/3 in my tree as I kick the tyres
although I dropped 1 following breakage and discussion on IRC.

-- 
Alex Bennée

Re: [PATCH-for-5.2 v4 00/17] ci: Move various jobs from Travis to GitLab CI
Posted by Philippe Mathieu-Daudé 3 years, 5 months ago
On 11/10/20 4:55 PM, Alex Bennée wrote:
> 
> Philippe Mathieu-Daudé <philmd@redhat.com> writes:
> 
>> We have various job covered on Travis-CI, but recommend the
>> community to use GitLab, so build failures are missed.
>>
>> We need help to move the jobs to GitLab (we will keep the s390x
>> and ppc64 containerized jobs on Travis as there is no similar
>> offer on GitLab). Start moving jobs.
>>
>> Resulting pipelines (96 jobs in 71 minutes and 4 seconds)
>>   https://gitlab.com/philmd/qemu/-/pipelines/213351318
>>   https://gitlab.com/philmd/qemu/-/pipelines/213378500
>>
>> Patches 1-3 are included because without them some jobs are
>> failing; but they will be merged via different trees.
> 
> Which trees? I'm currently holding 2/3 in my tree as I kick the tyres
> although I dropped 1 following breakage and discussion on IRC.

Well I'm not sure... The point of this series is not to fix GitLab
(as it will keep failing) but to move jobs from Travis to it. I
simply wanted to show a green GitLab.

I suppose they belong to Michael Tsirkin (vhost-user, ACPI).

Regards,

Phil.