From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, probb@iol.unh.edu,
Robin Jarry <rjarry@redhat.com>,
Aaron Conole <aconole@redhat.com>,
Michael Santana <maicolgabriel@hotmail.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Chengwen Feng <fengchengwen@huawei.com>
Subject: [PATCH] ci: fix unit tests with Fedora 37
Date: Fri, 18 Oct 2024 15:56:41 +0200 [thread overview]
Message-ID: <20241018135641.3546518-1-david.marchand@redhat.com> (raw)
This was detected in UNH envs.
In Fedora 37 and other distributions, meson 0.57 breaks when calling
the unit tests (probably because of an incompatibility with Python 3.11):
$ meson test -C build --suite DPDK:fast-tests
ninja: Entering directory `/root/dpdk/build'
ninja: no work to do.
Exception in callback TestHarness._run_tests.<locals>.test_done
(<Task finishe...explicitly.')>)
at /usr/local/lib/python3.11/site-packages/mesonbuild/mtest.py:1806
handle: <Handle TestHarness._run_tests.<locals>.test_done
(<Task finishe...explicitly.')>)
at /usr/local/lib/python3.11/site-packages/mesonbuild/mtest.py:1806>
Traceback (most recent call last):
File "/usr/lib64/python3.11/asyncio/events.py", line 80, in _run
self._context.run(self._callback, *self._args)
File "/usr/local/lib/python3.11/site-packages/mesonbuild/mtest.py",
line 1808, in test_done
f.result()
File "/usr/local/lib/python3.11/site-packages/mesonbuild/mtest.py",
line 1803, in run_test
res = await test.run(self)
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/mesonbuild/mtest.py",
line 1349, in run
await self._run_cmd(harness, cmd)
File "/usr/local/lib/python3.11/site-packages/mesonbuild/mtest.py",
line 1415, in _run_cmd
returncode, result, additional_error =
await p.wait(self.runobj.timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/mesonbuild/mtest.py",
line 1241, in wait
await try_wait_one(p.wait(), timeout=timeout)
File "/usr/local/lib/python3.11/site-packages/mesonbuild/mtest.py",
line 1132, in try_wait_one
await asyncio.wait(awaitables,
File "/usr/lib64/python3.11/asyncio/tasks.py", line 425, in wait
raise TypeError("Passing coroutines is forbidden, use tasks
explicitly.")
TypeError: Passing coroutines is forbidden, use tasks explicitly.
/usr/lib64/python3.11/asyncio/events.py:80: RuntimeWarning: coroutine
'Process.wait' was never awaited
self._context.run(self._callback, *self._args)
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
This issue is fixed by upgrading to 0.57.2.
Fixes: 6f3dbd306de0 ("build: increase minimum meson version to 0.57")
Suggested-by: Robin Jarry <rjarry@redhat.com>
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
Note: for now, this is a quick fix only for restoring unit tests in the
CI before rc1.
There is still the question of whether we should align the minimal
version to 0.57.2 too.
This can be rediscussed for rc2.
---
.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 8512a92b21..938d492cbb 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.57.0'
+sudo python3 -m pip install --upgrade 'meson==0.57.2'
# setup hugepages. error ignored because having hugepage is not mandatory.
cat /proc/meminfo
--
2.46.2
next reply other threads:[~2024-10-18 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 13:56 David Marchand [this message]
2024-10-18 14:04 ` Patrick Robb
2024-10-18 16:07 ` David Marchand
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=20241018135641.3546518-1-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=maicolgabriel@hotmail.com \
--cc=probb@iol.unh.edu \
--cc=rjarry@redhat.com \
--cc=thomas@monjalon.net \
/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).