[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cirrus-CI all red

From: Alex Bennée
Subject: Re: Cirrus-CI all red
Date: Tue, 09 Nov 2021 11:27:42 +0000
User-agent: mu4e 1.7.4; emacs 28.0.60

Daniel P. Berrangé <berrange@redhat.com> writes:

> On Tue, Nov 09, 2021 at 10:45:18AM +0100, Thomas Huth wrote:
>> On 09/11/2021 10.39, Philippe Mathieu-Daudé wrote:
>> > FYI, as of today, the latest merge history is red (last 10 days):
>> > https://cirrus-ci.com/github/qemu/qemu
>> > 
>> > If we want to keep using this, we should somehow plug it to
>> > GitLab-CI (i.e. Travis-CI is run as an external job there) so
>> > the project maintainer can notice job failures.
>> Well, considering that all the cirrus-run based jobs are currently failing
>> due to the non-working API token, that does not seem to work very well
>> either.
> Who owns the API token ? For other projects, this was addressed a while
> ago by refreshing the token. I would have tried this myself for QEMU
> but I don't have privileges on the QEMU projects in github/gitlab.

OK I've updated the token (after I figured out the path to it):

  - top right, Settings
  - scroll to bottom "Your GitHub Organizations"
  - click gear icon
  - scroll to API settings, click Generate New Token

It seems to be triggering the builds now although GitLab still reports
failures for some other reason now.

>> > Alternatively the windows job could be passed to GitLab:
>> > https://docs.gitlab.com/ee/ci/runners/runner_cloud/windows_runner_cloud.html
>> See:
>>  https://lists.gnu.org/archive/html/qemu-devel/2021-07/msg02474.html
>> ... the problem is again that the shared runners are only single-threaded,
>> so it's incredibly slow, especially if you have to re-install MSYS2 each
>> time. I once tried to improve the patch by caching the MSYS2 installation,
>> but it did not work that well either... (but if somebody wants to continue
>> my work, I can rebase and send it out again, just let me know).
> Potentially this is something where we can make sure of the Azure credits
> QEMU is getting, though it would require someone to figure out shared
> runner integration and maintain it...
> Regards,
> Daniel

Alex Bennée

reply via email to

[Prev in Thread] Current Thread [Next in Thread]