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 Developers" <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 0/4] hexagon: Add Docker image & testing to gitlab-ci
Date: Thu, 4 Mar 2021 13:59:40 +0000 [thread overview]
Message-ID: <CAHDbmO1wX74Gobmc1LCg6devmfm4iQPRZGwbGoEa8_418N3_yQ@mail.gmail.com> (raw)
In-Reply-To: <8735xbghho.fsf@linaro.org>
I of course meant 1 and 4 (skipping the gitlab bits)
On Thu, 4 Mar 2021 at 13:45, Alex Bennée <alex.bennee@linaro.org> wrote:
>
>
> Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
>
> > Hi,
> >
> > This series is a rework of the 'Add Dockerfile for hexagon' patch
> > from Alessandro/Brian that Taylor sent in v8:
> > https://www.mail-archive.com/qemu-devel@nongnu.org/msg780330.html
> > but adapted to mainstream.
>
> Queued patches 1 and 2 to testing/next, thanks.
>
> >
> > Gitlab shared runner are usually capped to 2/4 cores and timeout
> > after 2h30 to 3h. We need a beefy custom runner to get the image
> > built and stored in the registry. For now the image is added in
> > manual mode, hopping we'll have magic runners added some day to
> > build the image, then developers can directly pull it from the
> > registry.
> >
> > Alessandro Di Federico (2):
> > docker: Add Hexagon image
> > tests/tcg: Use Hexagon Docker image
> >
> > Philippe Mathieu-Daud=C3=A9 (2):
> > gitlab-ci: Pass optional EXTRA_FILES when building docker images
> > gitlab-ci: Build Hexagon cross-toolchain
> >
> > .gitlab-ci.d/containers.yml | 11 ++
> > tests/docker/Makefile.include | 2 +
> > .../dockerfiles/debian-hexagon-cross.docker | 23 +++
> > .../build-toolchain.sh | 141 ++++++++++++++++++
> > tests/tcg/configure.sh | 4 +
> > 5 files changed, 181 insertions(+)
> > create mode 100644 tests/docker/dockerfiles/debian-hexagon-cross.docker
> > create mode 100755 tests/docker/dockerfiles/debian-hexagon-cross.docker.d/bu=
> > ild-toolchain.sh
> >
> > --=20
> > 2.26.2
>
>
> --
> Alex Bennée
--
Alex Bennée
KVM/QEMU Hacker for Linaro
prev parent reply other threads:[~2021-03-04 14:02 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
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 [this message]
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=CAHDbmO1wX74Gobmc1LCg6devmfm4iQPRZGwbGoEa8_418N3_yQ@mail.gmail.com \
--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 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).