On Tue, Feb 23, 2021 at 04:17:23PM +0100, Philippe Mathieu-Daudé wrote: > 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 <cr...@redhat.com> > > Reviewed-by: Daniel P. Berrangé <berra...@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? >
The documentation on this series (previous patch) describes how one should go about settings the tags. Pasting it here for easier context: --- Following the registration, it's necessary to configure the runner tags, and optionally other configurations on the GitLab UI. Navigate to: * Settings (the gears like icon), then * CI/CD, then * Runners, and click on the "Expand" button, then * "Runners activated for this project", then * Click on the "Edit" icon (next to the "Lock" Icon) Under tags, add values matching the jobs a runner should run. For a Ubuntu 20.04 aarch64 system, the tags should be set as:: ubuntu_20.04,aarch64 Because the job definition at ``.gitlab-ci.d/custom-runners.yml`` would contain:: ubuntu-20.04-aarch64-all: tags: - ubuntu_20.04 - aarch64 --- Does that answer your question? > > + 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?): > The documentation explains that, saying that it's recommended to uncheck the "Run untagged jobs" check box. > $ 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: > You just need to take care of the runners you add. All the other jobs are assumed to be running on the shared runners. Regards, - Cleber.
signature.asc
Description: PGP signature