From: Patrick Robb <probb@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH v2] build: automatically report minimum meson version
Date: Thu, 15 May 2025 14:28:01 +0200 [thread overview]
Message-ID: <CAJvnSUAs=UvxGqj41JSMB3TibRrvLh0ZOGDBN7ffUkpGSvUyPA@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8z842+xoRs2P8YCrG9EvFD_S-aC-0oaiV_7Dz41qiVZnQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3788 bytes --]
On Thu, May 15, 2025 at 1:40 PM David Marchand <david.marchand@redhat.com>
wrote:
>
>
> Retests show the same error, so I think we are hitting the issue fixed
> with dbcd72f3fba0.
>
> Bumping the minimal version to 0.57.2 seems fine.
> I looked and can't find a distrib that ships meson 0.57.
> So either a user relies on the distrib version (with a version >=
> 0.58, from my quick search) or the distrib provided version is too old
> and then the user relies on pip.
>
>
FYI here's the stacktrace below which is not making it to the testlog on
the dashboard (something for UNH people to look at). But yes it's the same
issue fixed with dbcd72f3fba0babd2d801c2c63ee537df459df66
---------
Exception in callback TestHarness._run_tests.<locals>.test_done(<Task
finishe...explicitly.')>) at
/usr/local/lib/python3.12/site-packages/mesonbuild/mtest.py:1806
handle: <Handle TestHarness._run_tests.<locals>.test_done(<Task
finishe...explicitly.')>) at
/usr/local/lib/python3.12/site-packages/mesonbuild/mtest.py:1806>
Traceback (most recent call last):
File "/usr/lib64/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/local/lib/python3.12/site-packages/mesonbuild/mtest.py", line
1808, in test_done
f.result()
File "/usr/local/lib/python3.12/site-packages/mesonbuild/mtest.py", line
1803, in run_test
res = await test.run(self)
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/mesonbuild/mtest.py", line
1349, in run
await self._run_cmd(harness, cmd)
File "/usr/local/lib/python3.12/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.12/site-packages/mesonbuild/mtest.py", line
1241, in wait
await try_wait_one(p.wait(), timeout=timeout)
File "/usr/local/lib/python3.12/site-packages/mesonbuild/mtest.py", line
1132, in try_wait_one
await asyncio.wait(awaitables,
File "/usr/lib64/python3.12/asyncio/tasks.py", line 461, in wait
raise TypeError("Passing coroutines is forbidden, use tasks
explicitly.")
TypeError: Passing coroutines is forbidden, use tasks explicitly.
/usr/lib64/python3.12/asyncio/events.py:88: RuntimeWarning: coroutine
'Process.wait' was never awaited
self._context.run(self._callback, *self._args)
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/mesonbuild/mesonmain.py",
line 132, in run
return options.run_func(options)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/mesonbuild/mtest.py", line
1953, in run
return th.doit()
^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/mesonbuild/mtest.py", line
1641, in doit
self.run_tests(runners)
File "/usr/local/lib/python3.12/site-packages/mesonbuild/mtest.py", line
1780, in run_tests
loop.run_until_complete(self._run_tests(runners))
File "/usr/lib64/python3.12/asyncio/base_events.py", line 687, in
run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/mesonbuild/mtest.py", line
1871, in _run_tests
await complete(future)
File "/usr/local/lib/python3.12/site-packages/mesonbuild/mtest.py", line
1148, in complete
await future
TypeError: Passing coroutines is forbidden, use tasks explicitly.
Ok: 0
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 0
Timeout: 0
[-- Attachment #2: Type: text/html, Size: 4774 bytes --]
next prev parent reply other threads:[~2025-05-15 12:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 15:24 [RFC PATCH] " Bruce Richardson
2024-10-09 16:40 ` Stephen Hemminger
2024-10-14 16:31 ` Patrick Robb
2025-05-13 8:59 ` [PATCH v2] " Bruce Richardson
2025-05-15 7:09 ` David Marchand
2025-05-15 9:36 ` Bruce Richardson
2025-05-15 11:39 ` David Marchand
2025-05-15 12:28 ` Patrick Robb [this message]
2025-05-15 12:54 ` Bruce Richardson
2025-05-15 13:46 ` [PATCH v3] " Bruce Richardson
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='CAJvnSUAs=UvxGqj41JSMB3TibRrvLh0ZOGDBN7ffUkpGSvUyPA@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--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).