All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Fam Zheng" <fam@euphon.net>, "Brian Cain" <bcain@quicinc.com>,
	qemu-devel@nongnu.org, "Alessandro Di Federico" <ale.qemu@rev.ng>,
	"Taylor Simpson" <tsimpson@quicinc.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH 3/4] gitlab-ci: Build Hexagon cross-toolchain
Date: Thu, 04 Mar 2021 12:08:43 +0000	[thread overview]
Message-ID: <875z27glwo.fsf@linaro.org> (raw)
In-Reply-To: <20210228222314.304787-4-f4bug@amsat.org>


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

> Add a job to build the Debian based Hexagon cross-toolchain image.
>
> This image requires a lot of compute time, too much for the common
> shared runners. To avoid having the job to timeout, it has to be
> built with custom unlimited runner. For this reason we restrict this
> job to manual runs.
>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
>  .gitlab-ci.d/containers.yml | 10 ++++++++++
>  1 file changed, 10 insertions(+)
>
> diff --git a/.gitlab-ci.d/containers.yml b/.gitlab-ci.d/containers.yml
> index 7137cc4184d..ed57e02e769 100644
> --- a/.gitlab-ci.d/containers.yml
> +++ b/.gitlab-ci.d/containers.yml
> @@ -103,6 +103,16 @@ armhf-debian-cross-container:
>    variables:
>      NAME: debian-armhf-cross
>  
> +hexagon-debian-cross-container:
> +  <<: *container_job_definition
> +  stage: containers-layer2
> +  needs: ['amd64-debian10-container']
> +  when: manual
> +  timeout: 3h
> +  variables:
> +    NAME: debian-hexagon-cross
> +    EXTRA_FILES: tests/docker/dockerfiles/debian-hexagon-cross.docker.d/build-toolchain.sh
> +

We don't really want this - what we need is the ability to run the tests
for hexagon when the registry contains a built container that we have
manually pushed from a build machine:

  https://gitlab.com/qemu-project/qemu/container_registry/1759846

>  hppa-debian-cross-container:
>    <<: *container_job_definition
>    stage: containers-layer2


-- 
Alex Bennée


  reply	other threads:[~2021-03-04 12:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-28 22:23 [PATCH 0/4] hexagon: Add Docker image & testing to gitlab-ci Philippe Mathieu-Daudé
2021-02-28 22:23 ` [PATCH 1/4] docker: Add Hexagon image Philippe Mathieu-Daudé
2021-03-01 20:45   ` Brian Cain
2021-03-04 11:37   ` Alex Bennée
2021-02-28 22:23 ` [PATCH 2/4] gitlab-ci: Pass optional EXTRA_FILES when building docker images Philippe Mathieu-Daudé
2021-02-28 22:23 ` [PATCH 3/4] gitlab-ci: Build Hexagon cross-toolchain Philippe Mathieu-Daudé
2021-03-04 12:08   ` Alex Bennée [this message]
2021-03-04 17:43     ` Paolo Montesel via
2021-03-04 18:08       ` Alex Bennée
2021-02-28 22:23 ` [PATCH 4/4] tests/tcg: Use Hexagon Docker image Philippe Mathieu-Daudé
2021-02-28 22:27 ` [PATCH 0/4] hexagon: Add Docker image & testing to gitlab-ci no-reply
2021-03-01 13:25 ` Alessandro Di Federico via
2021-03-01 13:29   ` Philippe Mathieu-Daudé
2021-03-01 20:25 ` Taylor Simpson
2021-03-04 13:44 ` Alex Bennée
2021-03-04 13:59   ` 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=875z27glwo.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=ale.qemu@rev.ng \
    --cc=bcain@quicinc.com \
    --cc=f4bug@amsat.org \
    --cc=fam@euphon.net \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tsimpson@quicinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.