Re: [PATCH 0/5] QEMU Gating CI

[Cleber Rosa]

----- Original Message -----
> From: "Peter Maydell" <address@hidden>
> To: "Cleber Rosa" <address@hidden>
> Cc: "Fam Zheng" <address@hidden>, "Thomas Huth" <address@hidden>, "Beraldo 
> Leal" <address@hidden>, "Erik
> Skultety" <address@hidden>, "Alex Bennée" <address@hidden>, "Wainer 
> Moschetta" <address@hidden>,
> "QEMU Developers" <address@hidden>, "Wainer dos Santos Moschetta" 
> <address@hidden>, "Willian Rampazzo"
> <address@hidden>, "Philippe Mathieu-Daudé" <address@hidden>, "Eduardo 
> Habkost" <address@hidden>
> Sent: Monday, March 16, 2020 10:57:30 AM
> Subject: Re: [PATCH 0/5] QEMU Gating CI
> 
> On Mon, 16 Mar 2020 at 12:26, Cleber Rosa <address@hidden> wrote:
> > About the runners and the fact that the job is stuck without them,
> > the message seems straightforward enough, but I can't get to the
> > project configuration to look at the registered runners with my
> > current permissions (set as "developer").
> 
> I've moved you up to 'maintainer' status, hopefully that is
> sufficient to look at the relevant config ?
> 
> thanks
> -- PMM
> 
> 

Hi Peter,

Yes, that did the trick and I can now see the configuration.  What I can
*not* see is any "Specific Runner" configured.  So maybe:

1) The documentation I included is not clear enough about the fact that
setup steps need to be done on a machine so that it becomes a "Runner"

2) The (Ansible) playbooks (especially contrib/ci/orgs/qemu/gitlab-runner.yml)
is not working as intended

3) Some expectations misalignment on machines that would be available to run
those jobs

In any case, none of those should be big problems.  Please let me know what
you did/experienced/expected up to this point, and we can continue from there.

Regards,
- Cleber.