From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Cleber Rosa" <crosa@redhat.com>,
qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Daniel P . Berrangé" <berrange@redhat.com>
Cc: Fam Zheng <fam@euphon.net>,
Peter Maydell <peter.maydell@linaro.org>,
Thomas Huth <thuth@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Erik Skultety <eskultet@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
Andrea Bolognani <abologna@redhat.com>,
Wainer dos Santos Moschetta <wainersm@redhat.com>,
Willian Rampazzo <wrampazz@redhat.com>,
Beraldo Leal <bleal@redhat.com>
Subject: Re: [PATCH v5 4/4] Jobs based on custom runners: add job definitions for QEMU's machines
Date: Tue, 23 Feb 2021 16:17:23 +0100 [thread overview]
Message-ID: <21f882ba-21db-2d45-0e74-be27e1119355@redhat.com> (raw)
In-Reply-To: <20210219215838.752547-5-crosa@redhat.com>
On 2/19/21 10:58 PM, Cleber Rosa wrote:
> The QEMU project has two machines (aarch64 and s390x) that can be used
> for jobs that do build and run tests. This introduces those jobs,
> which are a mapping of custom scripts used for the same purpose.
>
> Signed-off-by: Cleber Rosa <crosa@redhat.com>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> .gitlab-ci.d/custom-runners.yml | 204 ++++++++++++++++++++++++++++++++
> 1 file changed, 204 insertions(+)
>
> diff --git a/.gitlab-ci.d/custom-runners.yml b/.gitlab-ci.d/custom-runners.yml
> index 3004da2bda..a9166c82a2 100644
> --- a/.gitlab-ci.d/custom-runners.yml
> +++ b/.gitlab-ci.d/custom-runners.yml
> @@ -12,3 +12,207 @@
> # strategy.
> variables:
> GIT_SUBMODULE_STRATEGY: recursive
> +
> +# All ubuntu-18.04 jobs should run successfully in an environment
> +# setup by the scripts/ci/setup/build-environment.yml task
> +# "Install basic packages to build QEMU on Ubuntu 18.04/20.04"
> +ubuntu-18.04-s390x-all-linux-static:
> + allow_failure: true
> + needs: []
> + stage: build
> + tags:
> + - ubuntu_18.04
> + - s390x
Where is this tag list filled upon registration?
> + rules:
> + - if: '$CI_COMMIT_BRANCH =~ /^staging/'
> + script:
> + # --disable-libssh is needed because of https://bugs.launchpad.net/qemu/+bug/1838763
> + # --disable-glusterfs is needed because there's no static version of those libs in distro supplied packages
> + - mkdir build
> + - cd build
> + - ../configure --enable-debug --static --disable-system --disable-glusterfs --disable-libssh
> + - make --output-sync -j`nproc`
> + - make --output-sync -j`nproc` check V=1
> + - make --output-sync -j`nproc` check-tcg V=1
Also this break the rest of the tests...
The first containers job (amd64-alpine-container) got
added to the custom runner and failed (because docker-dind
isn't there?):
$ export TAG="$CI_REGISTRY_IMAGE/qemu/$NAME:latest"
$ export COMMON_TAG="$CI_REGISTRY/qemu-project/qemu/$NAME:latest"
$ apk add python3
bash: line 110: apk: command not found
Running after_script 00:01
Running after script...
$ docker logout
Removing login credentials for https://index.docker.io/v1/
ERROR: Job failed: exit status 1
Do we need to restrict the other jobs to the Gitlab public
(x86) runners? Maybe as:
diff --git a/.gitlab-ci.d/containers.yml b/.gitlab-ci.d/containers.yml
@@ -1,6 +1,6 @@
.container_job_template: &container_job_definition
+ tags:
+ - gitlab-org-docker
image: docker:stable
stage: containers
services:
Daniel, you didn't hit this problem on the previous version
of this series?
Thanks,
Phil.
next prev parent reply other threads:[~2021-02-23 15:19 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 21:58 [PATCH v5 0/4] GitLab Custom Runners and Jobs (was: QEMU Gating CI) Cleber Rosa
2021-02-19 21:58 ` [PATCH v5 1/4] Jobs based on custom runners: documentation and configuration placeholder Cleber Rosa
2021-02-23 11:18 ` Alex Bennée
2021-02-23 11:25 ` Thomas Huth
2021-02-23 16:37 ` Philippe Mathieu-Daudé
2021-02-23 16:47 ` Cleber Rosa
2021-02-23 17:24 ` Philippe Mathieu-Daudé
2021-02-23 17:34 ` Philippe Mathieu-Daudé
2021-02-23 18:09 ` Cleber Rosa
2021-02-24 11:57 ` Philippe Mathieu-Daudé
2021-02-24 15:47 ` Cleber Rosa
2021-02-23 17:45 ` Daniel P. Berrangé
2021-02-23 21:34 ` Wainer dos Santos Moschetta
2021-02-19 21:58 ` [PATCH v5 2/4] Jobs based on custom runners: build environment docs and playbook Cleber Rosa
2021-02-22 19:36 ` Wainer dos Santos Moschetta
2021-02-23 14:01 ` Alex Bennée
2021-02-23 14:51 ` Erik Skultety
2021-02-23 15:17 ` Alex Bennée
2021-02-23 17:23 ` Cleber Rosa
2021-02-23 18:18 ` Alex Bennée
2021-02-23 17:13 ` Cleber Rosa
2021-02-23 15:01 ` Alex Bennée
2021-02-23 17:44 ` Cleber Rosa
2021-02-23 18:23 ` Alex Bennée
2021-02-23 19:47 ` Cleber Rosa
2021-02-23 17:08 ` Cleber Rosa
2021-02-23 18:16 ` Alex Bennée
2021-02-19 21:58 ` [PATCH v5 3/4] Jobs based on custom runners: docs and gitlab-runner setup playbook Cleber Rosa
2021-02-22 6:36 ` Erik Skultety
2021-02-22 20:35 ` Wainer dos Santos Moschetta
2021-02-23 13:52 ` Philippe Mathieu-Daudé
2021-02-23 13:55 ` Philippe Mathieu-Daudé
2021-02-23 14:14 ` Philippe Mathieu-Daudé
2021-02-23 15:15 ` Alex Bennée
2021-02-19 21:58 ` [PATCH v5 4/4] Jobs based on custom runners: add job definitions for QEMU's machines Cleber Rosa
2021-02-23 15:17 ` Philippe Mathieu-Daudé [this message]
2021-02-23 15:56 ` Daniel P. Berrangé
2021-02-23 16:41 ` Philippe Mathieu-Daudé
2021-02-23 18:25 ` Cleber Rosa
2021-02-24 12:00 ` Philippe Mathieu-Daudé
2021-02-24 15:54 ` Cleber Rosa
2021-02-23 18:21 ` Cleber Rosa
2021-02-23 15:27 ` Philippe Mathieu-Daudé
2021-02-23 15:35 ` Philippe Mathieu-Daudé
2021-02-23 15:45 ` Daniel P. Berrangé
2021-03-05 10:14 ` [PATCH v5 0/4] GitLab Custom Runners and Jobs (was: QEMU Gating CI) Philippe Mathieu-Daudé
2021-03-05 10:27 ` Philippe Mathieu-Daudé
2021-05-21 10:29 ` Alex Bennée
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=21f882ba-21db-2d45-0e74-be27e1119355@redhat.com \
--to=philmd@redhat.com \
--cc=abologna@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=eskultet@redhat.com \
--cc=fam@euphon.net \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=wrampazz@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).