Test pipeline:

  https://gitlab.com/abologna/libvirt/-/pipelines/548848259

Only patches 1-5 should be pushed until the issues outlined in

  https://listman.redhat.com/archives/libvir-list/2022-May/231851.html

have been addressed.

Changes from [v1]

  * handle integration tests separately;
  * don't stop publishing RPMs from the Fedora 35 job

[v1] https://listman.redhat.com/archives/libvir-list/2022-May/231838.html

Andrea Bolognani (7):
  ci: Drop Fedora 34
  ci: Refresh generated files
  ci: Add Fedora 36
  ci: Move MinGW jobs to Fedora 36
  ci: Don't mark any Fedora 36 job as optional
  ci: Add Fedora 36 to integration tests
  ci: Move upstream QEMU integration test to Fedora 36

 ...ile => fedora-36-cross-mingw32.Dockerfile} |   2 +-
 ...ile => fedora-36-cross-mingw64.Dockerfile} |   2 +-
 ...ora-34.Dockerfile => fedora-36.Dockerfile} |   3 +-
 ci/gitlab.yml                                 | 767 +-----------------
 ci/gitlab/build-templates.yml                 |  45 +
 ci/gitlab/builds.yml                          | 406 +++++++++
 ci/gitlab/container-templates.yml             |  52 ++
 ci/gitlab/containers.yml                      | 325 ++++++++
 ci/gitlab/sanity-checks.yml                   |  18 +
 ci/integration.yml                            |  24 +-
 ci/manifest.yml                               |   5 +-
 11 files changed, 869 insertions(+), 780 deletions(-)
 rename ci/containers/{fedora-35-cross-mingw32.Dockerfile => fedora-36-cross-mingw32.Dockerfile} (98%)
 rename ci/containers/{fedora-35-cross-mingw64.Dockerfile => fedora-36-cross-mingw64.Dockerfile} (98%)
 rename ci/containers/{fedora-34.Dockerfile => fedora-36.Dockerfile} (97%)
 create mode 100644 ci/gitlab/build-templates.yml
 create mode 100644 ci/gitlab/builds.yml
 create mode 100644 ci/gitlab/container-templates.yml
 create mode 100644 ci/gitlab/containers.yml
 create mode 100644 ci/gitlab/sanity-checks.yml

-- 
2.35.3

On Thu, May 26, 2022 at 04:01:45PM +0200, Andrea Bolognani wrote:
> Test pipeline:
> 
>   https://gitlab.com/abologna/libvirt/-/pipelines/548848259
> 
> Only patches 1-5 should be pushed until the issues outlined in

Go ahead and push 1-5 ;).

Erik

On Thu, May 26, 2022 at 04:24:41PM +0200, Erik Skultety wrote:
> On Thu, May 26, 2022 at 04:01:45PM +0200, Andrea Bolognani wrote:
> > Test pipeline:
> >
> >   https://gitlab.com/abologna/libvirt/-/pipelines/548848259
> >
> > Only patches 1-5 should be pushed until the issues outlined in
>
> Go ahead and push 1-5 ;).

Can I push the remaining two patches now, or are the issues that made
it not possible at the time still relevant?

-- 
Andrea Bolognani / Red Hat / Virtualization

On Tue, Jun 07, 2022 at 02:34:50AM -0700, Andrea Bolognani wrote:
> On Thu, May 26, 2022 at 04:24:41PM +0200, Erik Skultety wrote:
> > On Thu, May 26, 2022 at 04:01:45PM +0200, Andrea Bolognani wrote:
> > > Test pipeline:
> > >
> > >   https://gitlab.com/abologna/libvirt/-/pipelines/548848259
> > >
> > > Only patches 1-5 should be pushed until the issues outlined in
> >
> > Go ahead and push 1-5 ;).
> 
> Can I push the remaining two patches now, or are the issues that made
> it not possible at the time still relevant?

Yes, the problem still persists.

Regards,
Erik

On Tue, Jun 07, 2022 at 01:06:41PM +0200, Erik Skultety wrote:
> On Tue, Jun 07, 2022 at 02:34:50AM -0700, Andrea Bolognani wrote:
> > On Thu, May 26, 2022 at 04:24:41PM +0200, Erik Skultety wrote:
> > > On Thu, May 26, 2022 at 04:01:45PM +0200, Andrea Bolognani wrote:
> > > > Test pipeline:
> > > >
> > > >   https://gitlab.com/abologna/libvirt/-/pipelines/548848259
> > > >
> > > > Only patches 1-5 should be pushed until the issues outlined in
> > >
> > > Go ahead and push 1-5 ;).
> > 
> > Can I push the remaining two patches now, or are the issues that made
> > it not possible at the time still relevant?
> 
> Yes, the problem still persists.

FYI, once we merge [1] we can merge this one as well.
[1] https://listman.redhat.com/archives/libvir-list/2022-June/232322.html

Regards,
Erik

On Thu, Jun 09, 2022 at 08:11:17AM +0200, Erik Skultety wrote:
> On Tue, Jun 07, 2022 at 01:06:41PM +0200, Erik Skultety wrote:
> > On Tue, Jun 07, 2022 at 02:34:50AM -0700, Andrea Bolognani wrote:
> > > Can I push the remaining two patches now, or are the issues that made
> > > it not possible at the time still relevant?
> >
> > Yes, the problem still persists.
>
> FYI, once we merge [1] we can merge this one as well.
> [1] https://listman.redhat.com/archives/libvir-list/2022-June/232322.html

Those are in now. Can you confirm I can push the remaining patches?

-- 
Andrea Bolognani / Red Hat / Virtualization

On Thu, Jun 09, 2022 at 07:51:45AM -0400, Andrea Bolognani wrote:
> On Thu, Jun 09, 2022 at 08:11:17AM +0200, Erik Skultety wrote:
> > On Tue, Jun 07, 2022 at 01:06:41PM +0200, Erik Skultety wrote:
> > > On Tue, Jun 07, 2022 at 02:34:50AM -0700, Andrea Bolognani wrote:
> > > > Can I push the remaining two patches now, or are the issues that made
> > > > it not possible at the time still relevant?
> > >
> > > Yes, the problem still persists.
> >
> > FYI, once we merge [1] we can merge this one as well.
> > [1] https://listman.redhat.com/archives/libvir-list/2022-June/232322.html
> 
> Those are in now. Can you confirm I can push the remaining patches?

Sure, to both:
Reviewed-by: Erik Skultety <eskultet@redhat.com>