From: Wainer dos Santos Moschetta <wainersm@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Laurent Vivier" <laurent@vivier.eu>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH v2 2/2] gitlab-ci: Test building linux-user targets on CentOS 7
Date: Thu, 21 Jan 2021 14:45:11 -0300 [thread overview]
Message-ID: <88c1ddbd-d93d-01e4-abfa-78b395ac4d36@redhat.com> (raw)
In-Reply-To: <20210121172829.1643620-3-f4bug@amsat.org>
Hi,
On 1/21/21 2:28 PM, Philippe Mathieu-Daudé wrote:
> Add a configuration tested by Peter Maydell (see [1] and [2])
> but not covered in our CI [3]:
>
> [705/2910] Compiling C object libqemu-arm-linux-user.fa.p/linux-user_strace.c.o
> FAILED: libqemu-arm-linux-user.fa.p/linux-user_strace.c.o
> ../linux-user/strace.c: In function 'do_print_sockopt':
> ../linux-user/strace.c:2831:14: error: 'IPV6_ADDR_PREFERENCES' undeclared (first use in this function)
> case IPV6_ADDR_PREFERENCES:
Why the following builder did not catch that issue?
build-user:
<<: *native_build_job_definition
variables:
IMAGE: debian-all-test-cross
CONFIGURE_ARGS: --disable-tools --disable-system
MAKE_CHECK_ARGS: check-tcg
> ^
>
> This job currently takes 31 minutes 32 seconds ([4]).
>
> [1] https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg05086.html
> [2] https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg05379.html
> [3] https://gitlab.com/philmd/qemu/-/jobs/977408284
> [4] https://gitlab.com/philmd/qemu/-/jobs/978223286
>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> .gitlab-ci.yml | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index de3a3d25b58..af4d74757d8 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -411,6 +411,13 @@ build-user-plugins:
> MAKE_CHECK_ARGS: check-tcg
> timeout: 1h 30m
>
> +build-user-centos7:
> + <<: *native_build_job_definition
> + variables:
> + IMAGE: centos7
> + CONFIGURE_ARGS: --disable-system --disable-tools --disable-docs
> + MAKE_CHECK_ARGS: check-tcg
> +
> build-some-softmmu-plugins:
> <<: *native_build_job_definition
> variables:
next prev parent reply other threads:[~2021-01-21 17:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 17:28 [PATCH v2 0/2] gitlab-ci: Test linux-user on CentOS 7 Philippe Mathieu-Daudé
2021-01-21 17:28 ` [PATCH v2 1/2] tests/docker: Install static libc package in " Philippe Mathieu-Daudé
2021-01-21 18:25 ` Thomas Huth
2021-01-21 18:30 ` Wainer dos Santos Moschetta
2021-01-21 17:28 ` [PATCH v2 2/2] gitlab-ci: Test building linux-user targets on " Philippe Mathieu-Daudé
2021-01-21 17:45 ` Wainer dos Santos Moschetta [this message]
2021-01-21 18:20 ` Philippe Mathieu-Daudé
2021-01-21 18:29 ` Wainer dos Santos Moschetta
2021-01-21 18:25 ` Thomas Huth
2021-01-21 18:33 ` Wainer dos Santos Moschetta
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=88c1ddbd-d93d-01e4-abfa-78b395ac4d36@redhat.com \
--to=wainersm@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--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).