Bug 1969310
Summary: | sudo fails to build in Fedora 35+: Expectation failed at ./regress/testhelpers.c:98: | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tomáš Hrnčiar <thrnciar> |
Component: | sudo | Assignee: | Radovan Sroka <rsroka> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 35 | CC: | alakatos, cstratak, kzak, mattdm, mhroncok, peter, rsroka, thrnciar, tosykora, zfridric |
Target Milestone: | --- | ||
Target Release: | --- | ||
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: | 2021-08-25 20:29:29 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1890881, 1927309, 1992484 |
Description
Tomáš Hrnčiar
2021-06-08 07:43:31 UTC
Could you please respond and rebuild sudo with Python 3.10? Thanks Is this runpath really invalid? /usr/libexec/sudo (In reply to Miro Hrončok from comment #2) > Is this runpath really invalid? /usr/libexec/sudo The issue is fixed on the latest rpm, which should land in rawhide quite soon. Attempting a build with RPM 4.17 beta which should have fixed bz1973304. OK, that was fixed, but only to reveal the real issue. Expectation failed at ./regress/testhelpers.c:98: actual is <<sudo.debug was called with arguments: (DEBUG.ERROR, 'My demo purpose plugin shows this ERROR level debug message') sudo.debug was called with arguments: (DEBUG.INFO, 'My demo purpose plugin shows this INFO level debug message') LogHandler.emit was called LogHandler.emit was called sudo.options_as_dict was called with arguments: (('ModulePath=SRC_DIR/example_debugging.py', 'ClassName=DebugDemoPlugin'),) sudo.options_as_dict returned result: [('ClassName', 'DebugDemoPlugin'), ('ModulePath', 'SRC_DIR/example_debugging.py')] >>: actual_content expected to be <<sudo.debug was called with arguments: (<DEBUG.ERROR: 2>, 'My demo purpose plugin shows this ERROR level debug message') sudo.debug was called with arguments: (<DEBUG.INFO: 6>, 'My demo purpose plugin shows this INFO level debug message') LogHandler.emit was called LogHandler.emit was called sudo.options_as_dict was called with arguments: (('ModulePath=SRC_DIR/example_debugging.py', 'ClassName=DebugDemoPlugin'),) sudo.options_as_dict returned result: [('ClassName', 'DebugDemoPlugin'), ('ModulePath', 'SRC_DIR/example_debugging.py')] >>: expected_output Expectation failed at ./regress/testhelpers.c:228: actual is <<0>>: verify_content(stored_str, reference_path) not expected to be <<0>>: 0 Expectation failed at ./regress/check_python_examples.c:555: actual is <<0>>: verify_log_lines(expected_path("check_example_debugging_%s.log", debug_spec)) not expected to be <<0>>: 0 FAILED: testcase check_example_debugging("c_calls@diag") at ./regress/check_python_examples.c:1591 The output of the plugin: The error output of the plugin: Running test check_example_debugging("c_calls@info") ... Expectation failed at ./regress/testhelpers.c:98: actual is <<__init__ @ SRC_DIR/example_debugging.py:58 calls C function: sudo.debug was called with arguments: (DEBUG.ERROR, 'My demo purpose plugin shows this ERROR level debug message') __init__ @ SRC_DIR/example_debugging.py:63 calls C function: sudo.debug was called with arguments: (DEBUG.INFO, 'My demo purpose plugin shows this INFO level debug message') handle @ logging/__init__.py calls C function: LogHandler.emit was called handle @ logging/__init__.py calls C function: LogHandler.emit was called __init__ @ SRC_DIR/example_debugging.py:85 calls C function: sudo.options_as_dict was called with arguments: (('ModulePath=SRC_DIR/example_debugging.py', 'ClassName=DebugDemoPlugin'),) sudo.options_as_dict returned result: [('ClassName', 'DebugDemoPlugin'), ('ModulePath', 'SRC_DIR/example_debugging.py')] >>: actual_content expected to be <<__init__ @ SRC_DIR/example_debugging.py:58 calls C function: sudo.debug was called with arguments: (<DEBUG.ERROR: 2>, 'My demo purpose plugin shows this ERROR level debug message') __init__ @ SRC_DIR/example_debugging.py:63 calls C function: sudo.debug was called with arguments: (<DEBUG.INFO: 6>, 'My demo purpose plugin shows this INFO level debug message') handle @ logging/__init__.py calls C function: LogHandler.emit was called handle @ logging/__init__.py calls C function: LogHandler.emit was called __init__ @ SRC_DIR/example_debugging.py:85 calls C function: sudo.options_as_dict was called with arguments: (('ModulePath=SRC_DIR/example_debugging.py', 'ClassName=DebugDemoPlugin'),) sudo.options_as_dict returned result: [('ClassName', 'DebugDemoPlugin'), ('ModulePath', 'SRC_DIR/example_debugging.py')] >>: expected_output Expectation failed at ./regress/testhelpers.c:228: actual is <<0>>: verify_content(stored_str, reference_path) not expected to be <<0>>: 0 Expectation failed at ./regress/check_python_examples.c:555: actual is <<0>>: verify_log_lines(expected_path("check_example_debugging_%s.log", debug_spec)) not expected to be <<0>>: 0 FAILED: testcase check_example_debugging("c_calls@info") at ./regress/check_python_examples.c:1592 Hence, restoring the needinfo. Upgrading sudo to version 1.9.7+ should resolve the Python 3.10 problem. See changelog at https://www.sudo.ws/stable.html#1.9.7p1 Dear Maintainer, your package has an open Fails To Build From Source bug for Fedora 35. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. If you have already fixed this issue, please close this Bugzilla report. Following the policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks (not sooner than 2021-08-03). A week before the mass branching of Fedora 36 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 34 will be retired regardless of the status of this bug. [1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html The package no longer fails to build with Python 3.10.0b4. I will take care of the rebuild. Please note that the standard library enum implementation was reverted upstream to the Python 3.9 version; if the failure was enum related (such as tests expecting a specific Enum.__repr__ value) it will likely happen again with Python 3.11. https://mail.python.org/archives/list/python-dev@python.org/message/LSTMFAPSPD3BGZ4D6HQFODXZVB3PLYKF/ This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35. I am pretty sure this is fixed. I just built sudo for rawhide with no problems. |