Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2230860

Summary:	traceback while running meson test with valgrind
Product:	Red Hat Enterprise Linux 9	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	meson	Assignee:	meson-maint
Status:	CLOSED MIGRATED	QA Contact:	Tomas Pelka <tpelka>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	bstinson, desktop-qa-list, jwboyer, wtaymans
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-15 19:06:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sandro Bonazzola 2023-08-10 07:56:27 UTC

Description of problem:
while running meson test with coverage enabled for hirte project I got:

```console
meson test --wrap='valgrind --leak-check=full --error-exitcode=1 --track-origins=yes' -C builddir
ninja: Entering directory `/root/hirte/builddir'
ninja: no work to do.
 1/11 string-util_test             OK              9.72s
 2/11 time-util_test               OK              0.56s
 3/11 list_test                    OK             11.26s
 4/11 parse-util_test              OK             13.65s
Exception in callback TestHarness._run_tests.<locals>.test_done(<Task finishe...imeoutError()>) at /usr/lib/python3.9/site-packages/mesonbuild/mtest.py:1882
handle: <Handle TestHarness._run_tests.<locals>.test_done(<Task finishe...imeoutError()>) at /usr/lib/python3.9/site-packages/mesonbuild/mtest.py:1882>
Traceback (most recent call last):
  File "/usr/lib64/python3.9/asyncio/subprocess.py", line 135, in wait
    return await self._transport._wait()
  File "/usr/lib64/python3.9/asyncio/base_subprocess.py", line 235, in _wait
    return await waiter
asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib64/python3.9/asyncio/tasks.py", line 490, in wait_for
    return fut.result()
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/lib64/python3.9/asyncio/events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 1884, in test_done
    f.result()
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 1879, in run_test
    res = await test.run(self)
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 1416, in run
    await self._run_cmd(harness, cmd)
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 1483, in _run_cmd
    await p.wait(self.runobj)
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 1305, in wait
    test.additional_error += await self._kill() or ''
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 1266, in _kill
    await asyncio.wait_for(p.wait(), timeout=0.5)
  File "/usr/lib64/python3.9/asyncio/tasks.py", line 492, in wait_for
    raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError

Ok:                 4   
Expected Fail:      0   
Fail:               0   
Unexpected Pass:    0   
Skipped:            0   
Timeout:            0   

Full log written to /root/hirte/builddir/meson-logs/testlog-valgrind.txt
Traceback (most recent call last):
  File "/usr/lib64/python3.9/asyncio/subprocess.py", line 135, in wait
    return await self._transport._wait()
  File "/usr/lib64/python3.9/asyncio/base_subprocess.py", line 235, in _wait
    return await waiter
asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib64/python3.9/asyncio/tasks.py", line 490, in wait_for
    return fut.result()
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/mesonbuild/mesonmain.py", line 153, in run
    return options.run_func(options)
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 2040, in run
    return th.doit()
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 1717, in doit
    self.run_tests(runners)
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 1856, in run_tests
    loop.run_until_complete(self._run_tests(runners))
  File "/usr/lib64/python3.9/asyncio/base_events.py", line 647, in run_until_complete
    return future.result()
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 1953, in _run_tests
    await complete_all(futures)
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 1199, in complete_all
    check_futures(done)
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 1189, in check_futures
    f.result()
  File "/usr/lib64/python3.9/asyncio/events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 1884, in test_done
    f.result()
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 1879, in run_test
    res = await test.run(self)
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 1416, in run
    await self._run_cmd(harness, cmd)
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 1483, in _run_cmd
    await p.wait(self.runobj)
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 1305, in wait
    test.additional_error += await self._kill() or ''
  File "/usr/lib/python3.9/site-packages/mesonbuild/mtest.py", line 1266, in _kill
    await asyncio.wait_for(p.wait(), timeout=0.5)
  File "/usr/lib64/python3.9/asyncio/tasks.py", line 492, in wait_for
    raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError

ERROR: Unhandled python exception

    This is a Meson bug and should be reported!
make: *** [Makefile:29: test-with-valgrind-coverage] Errore 2
```

Version-Release number of selected component (if applicable):
meson-0.63.3-1.el9.noarch

Comment 1 RHEL Program Management 2023-09-15 18:45:11 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-09-15 19:06:59 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.