From: "Alex Bennée" <alex.bennee@linaro.org>
To: Claudio Fontana <cfontana@suse.de>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: check-tcg errors (build-user, build-user-plugins) again
Date: Wed, 02 Dec 2020 11:16:04 +0000 [thread overview]
Message-ID: <87v9dksbkb.fsf@linaro.org> (raw)
In-Reply-To: <f14c22bf-aecb-3e38-347b-1b9119ad8baa@suse.de>
Claudio Fontana <cfontana@suse.de> writes:
> Hi Alex and all,
>
> when trying to use check-tcg (master), I am getting often these errors:
>
> $ ../configure --disable-system --disable-tools
>
> $ make -j12 check-tcg
>
> ERRO[0000] cannot find mappings for user claudio: No subgid ranges found for group "claudio" in /etc/subgid
> ERRO[0000] cannot find mappings for user claudio: No subgid ranges found for group "claudio" in /etc/subgid
> ERRO[0000] cannot find mappings for user claudio: No subgid ranges found for group "claudio" in /etc/subgid
> Trying to pull registry.gitlab.com/qemu-project/qemu/qemu/debian11...
> Trying to pull registry.gitlab.com/qemu-project/qemu/qemu/fedora-cris-cross...
> Trying to pull registry.gitlab.com/qemu-project/qemu/qemu/debian10...
> ERRO[0000] cannot find mappings for user claudio: No subgid ranges found for group "claudio" in /etc/subgid
>
> [...]
> TEST linux-test on x86_64
> timeout: failed to run command ‘/home/claudio/git/qemu/build/qemu-x86_64’timeout: : No such file or directoryfailed to run command ‘/home/claudio/git/qemu/build/qemu-x86_64’
>
> [...]
>
>
> Is there some pre-configuration on the host necessary to be able to
> run check-tcg?
There shouldn't be but those errors remind me of some of the tweaks I
had to make to me Gentoo system when using podman (instead of docker).
In the end I think I just ended up adding the lines:
alex:100000:65536
to /etc/subgid and /etc/subgid-
Marc-André may have some better pointers as he added podman support to
the builder scripts.
The main difference between the images on the registry and the local
versions is most add the current user so there is a clean mapping
between the container user and the host file-system. It's the last step
of the build so we still use the cached layers from the registry
versions.
> I see these errors in gitlab also for
>
> build-user
> build-user-plugin
>
> Maybe this is what Philippe mentioned before though, that this is
> expected at the moment due to a temporary Meson shortcoming?
That is odd - I'm not seeing anything like that on the master builds:
https://gitlab.com/qemu-project/qemu/-/jobs/883985106
https://gitlab.com/qemu-project/qemu/-/jobs/883985113
AFAIK GitLab is still using Docker to build it's containers (albeit with
BUILDKIT enabled).
>
> Ciao,
>
> Claudio
--
Alex Bennée
next prev parent reply other threads:[~2020-12-02 11:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 9:32 check-tcg errors (build-user, build-user-plugins) again Claudio Fontana
2020-12-02 11:16 ` Alex Bennée [this message]
2020-12-02 11:25 ` Claudio Fontana
2020-12-02 12:52 ` Alex Bennée
2020-12-02 14:24 ` Claudio Fontana
2020-12-02 14:25 ` Philippe Mathieu-Daudé
2021-01-10 21:17 ` check-tcg HOWTO? Claudio Fontana
2021-01-11 13:35 ` Alex Bennée
2021-01-11 14:47 ` Claudio Fontana
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=87v9dksbkb.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=cfontana@suse.de \
--cc=marcandre.lureau@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).