From: Richard Henderson <richard.henderson@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Thomas Huth" <thuth@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: gitlab containers are broken
Date: Thu, 4 Feb 2021 07:36:19 -1000 [thread overview]
Message-ID: <9e716df9-3be3-4c79-dff3-e6475b13fdc5@linaro.org> (raw)
In-Reply-To: <20210204100009.GE549438@redhat.com>
On 2/4/21 12:00 AM, Daniel P. Berrangé wrote:
>>> Hmm. Is there any way to get the full output of the container build? At
>>> present it's being truncated:
>>>
>>> #7 [4/5] RUN yum install -y bzip2 bzip2-devel ccache csnappy-de...
>>>
>>>
>>> In particular, I'm trying to add a new test, and I have added libffi-devel.i686
>>> to the fedora-i386-cross.docker file, but then the actual build fails because
>>> the libffi header file is missing.
...
> Alternatively just make your changes to the dockerfiles and thne push
> the branch to gitlab. Gitlab will run the build and you can pull down
> the docker image from your fork's docker registry
That's what I did, with the results as described above.
r~
next prev parent reply other threads:[~2021-02-04 18:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 23:04 gitlab containers are broken Richard Henderson
2021-02-04 6:03 ` Thomas Huth
2021-02-04 6:27 ` Richard Henderson
2021-02-04 8:08 ` Thomas Huth
2021-02-04 10:00 ` Daniel P. Berrangé
2021-02-04 17:36 ` Richard Henderson [this message]
2021-02-04 17:37 ` Daniel P. Berrangé
2021-02-04 18:27 ` Richard Henderson
2021-02-04 18:58 ` Daniel P. Berrangé
2021-02-04 19:09 ` Richard Henderson
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=9e716df9-3be3-4c79-dff3-e6475b13fdc5@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).