From: Thomas Monjalon <thomas@monjalon.net>
To: bruce.richardson@intel.com
Cc: dev@dpdk.org, honnappa.nagarahalli@arm.com, jerinj@marvell.com,
hemant.agrawal@nxp.com,
David Marchand <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] devtools: reduce list of Arm builds tested with meson
Date: Thu, 21 Nov 2019 00:47:18 +0100 [thread overview]
Message-ID: <1949282.HhDP2dcKvQ@xps> (raw)
In-Reply-To: <20191120234222.23540-1-thomas@monjalon.net>
21/11/2019 00:42, Thomas Monjalon:
> The list of Arm configs is growing:
> config/arm/arm64_armada_linux_gcc
> config/arm/arm64_armv8_linux_gcc
> config/arm/arm64_bluefield_linux_gcc
> config/arm/arm64_dpaa_linux_gcc
> config/arm/arm64_emag_linux_gcc
> config/arm/arm64_n1sdp_linux_gcc
> config/arm/arm64_octeontx2_linux_gcc
> config/arm/arm64_thunderx2_linux_gcc
> config/arm/arm64_thunderx_linux_gcc
>
> In order to keep testing time reasonable,
> and also because n1sdp is merged without a related fix in tests,
> the list of configs is reduced in the script test-meson-builds.sh.
>
> The list of tested Arm builds becomes:
> build-arm64-host-clang (armv8a)
> build-arm64-bluefield
> build-arm64-dpaa
> build-arm64-octeontx2
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> Acked-by: David Marchand <david.marchand@redhat.com>
It is keeping one target per vendor (Arm, Marvell, Mellanox, NXP).
I hope it is enough.
When rebuilding all, we had 10 Arm targets (including the host-clang),
it is really too much in my opinion. It cuts from 10 to 4.
And first benefit is to skip n1sdp which we should fix properly in -rc4.
Applied quickly before closing -rc3.
prev parent reply other threads:[~2019-11-20 23:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 23:42 Thomas Monjalon
2019-11-20 23:47 ` Thomas Monjalon [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=1949282.HhDP2dcKvQ@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.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).