From: Patrick Robb <probb@iol.unh.edu>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, david.marchand@redhat.com,
zhoumin@loongson.cn, aconole@redhat.com,
rajesh.t.puttaswamy@intel.com, ci@dpdk.org
Subject: Re: [PATCH] Increasing ci meson version to .57
Date: Tue, 8 Oct 2024 15:33:43 -0400 [thread overview]
Message-ID: <CAJvnSUBo49P1JofvtnKOxYffKPboYyt_5bTqbmWDKd=i6e8A1w@mail.gmail.com> (raw)
In-Reply-To: <20241008192543.800702-1-probb@iol.unh.edu>
[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]
Oh, I guess I should have mentioned that I did "test" this for good
measure, by spinning up a base ubuntu 20.04 container, running the
linux-setup.sh with this change, and did a dpdk build.
Tested-by: Patrick Robb <probb@iol.unh.edu>
On Tue, Oct 8, 2024 at 3:27 PM Patrick Robb <probb@iol.unh.edu> wrote:
> There is a proposed increase in the minimum meson version to .57
> This patch aligns the linux setup ci script with this change.
>
> Signed-off-by: Patrick Robb <probb@iol.unh.edu>
> ---
> .ci/linux-setup.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.ci/linux-setup.sh b/.ci/linux-setup.sh
> index 975bf32144..c7b6a86d38 100755
> --- a/.ci/linux-setup.sh
> +++ b/.ci/linux-setup.sh
> @@ -4,7 +4,7 @@
> [ "$(id -u)" != '0' ] || alias sudo=
>
> # need to install as 'root' since some of the unit tests won't run
> without it
> -sudo python3 -m pip install --upgrade 'meson==0.53.2'
> +sudo python3 -m pip install --upgrade 'meson==0.57'
>
> # setup hugepages. error ignored because having hugepage is not mandatory.
> cat /proc/meminfo
> --
> 2.46.1
>
>
[-- Attachment #2: Type: text/html, Size: 1645 bytes --]
next prev parent reply other threads:[~2024-10-08 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 19:25 Patrick Robb
2024-10-08 19:33 ` Patrick Robb [this message]
2024-10-08 20:05 ` Bruce Richardson
2024-10-08 20:11 ` Patrick Robb
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='CAJvnSUBo49P1JofvtnKOxYffKPboYyt_5bTqbmWDKd=i6e8A1w@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=rajesh.t.puttaswamy@intel.com \
--cc=zhoumin@loongson.cn \
/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).