Re: [PATCH v3] travis-ci: Disable C++ optional objects on AArch64 container

[Alex Bennée]

Philippe Mathieu-Daudé <f4bug@amsat.org> writes:

> On 2/9/21 2:41 PM, Peter Maydell wrote:
>> On Tue, 9 Feb 2021 at 13:32, Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
>>> Migration of this job is pending of Cleber's possibility to add an AArch64
>>> runner to Gitlab-CI, right? Then we need someone to support and maintain
>>> the hardware... I don't think anybody volunteered.
>> 
>> We have the hardware already. Effectively Alex is maintaining it...
>
> I missed to read if Alex volunteered for this task but am certainly
> happy if he is :) Although this should be documented somewhere (who
> to contact if the AArch64 runner starts to fail?).

I'm listed on:

  https://wiki.qemu.org/AdminContacts

and have the root keys. I had given Cleber access to get the runners up
and running which I thought they were:

  3291365 ?        Ssl    8:41 /usr/bin/gitlab-runner run --working-directory 
/home/gitlab-runner --config /etc/gitlab-runner/config.toml --service 
gitlab-runner --user gitlab-runner

I'm not sure what else is needed on the HW side, it's just waiting for
the gitlab bits to be plumbed in.

I should mention the HW is due to be upgraded in the next few weeks but
I don't expect the upgrade to affect the way we plan to use the machine.

> Assuming Cleber's runner script is merged and working on the AArch64
> runner, then we need to figure how contributors can use it.
> Assuming this runner will be registered under the QEMU organization
> namespace in Gitlab, then contributors would have to open a Merge
> Request to trigger the CI jobs (similarly to when you push to the
> /staging branch). Then we would cancel the MR. We can ask contributors
> to cancel their MR once testing done.
>
> Midway could be having maintainers opening such MR?
>
> I have no idea, just asking questions to see if other have ideas or
> see the big picture here.
>
> Regards,
>
> Phil.


-- 
Alex Bennée