[Top][All Lists]

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

Re: [PATCH 0/5] QEMU Gating CI

From: Cleber Rosa
Subject: Re: [PATCH 0/5] QEMU Gating CI
Date: Mon, 16 Mar 2020 08:26:46 -0400 (EDT)

----- Original Message -----
> From: "Peter Maydell" <address@hidden>
> To: "Cleber Rosa" <address@hidden>
> Cc: "Alex Bennée" <address@hidden>, "QEMU Developers" <address@hidden>, "Fam 
> Zheng" <address@hidden>,
> "Eduardo Habkost" <address@hidden>, "Beraldo Leal" <address@hidden>, 
> "Philippe Mathieu-Daudé"
> <address@hidden>, "Thomas Huth" <address@hidden>, "Wainer dos Santos 
> Moschetta" <address@hidden>, "Erik
> Skultety" <address@hidden>, "Willian Rampazzo" <address@hidden>, "Wainer 
> Moschetta" <address@hidden>
> Sent: Monday, March 16, 2020 8:12:16 AM
> Subject: Re: [PATCH 0/5] QEMU Gating CI
> On Mon, 16 Mar 2020 at 12:04, Cleber Rosa <address@hidden> wrote:
> > A few possible reasons come to my mind:
> >
> > 1) It usually takes a few seconds after the push for the pipeline to
> >
> > 2) If you've pushed to a repo different than gitlab.com/qemu-project/qemu,
> >    you'd have to tweak the project ID (-p|--project-id).
> >
> > 3) The local branch is not called "staging", so the script can not find the
> >    commit ID, in that case you can use -c|--commit.
> Yes, the local branch is something else for the purposes of
> testing this series. But using --commit doesn't work either:
> $ ./contrib/ci/scripts/gitlab-pipeline-status --verbose --commit
> 81beaaab0851fe8c4db971 --wait
> ERROR: No pipeline found
> failure

This may be a bug in the script because I was not expecting two
pipelines for the same commit. Checking...

> On the web UI:
> https://gitlab.com/qemu-project/qemu/pipelines
> the pipelines are marked "stuck" (I don't know why there
> are two of them for the same commit); drilling down,
> the build part has completed but all the test parts are
> pending with "This job is stuck because you don't have
> any active runners online with any of these tags assigned
> to them" type messages.

I had also not come across the duplicate pipelines, so I'm trying
to understand what's that about.

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").

> thanks
> -- PMM

- Cleber.

reply via email to

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