Bug 2259549
| Summary: | python-robotframework fails to build with Python 3.13: ZeroDivisionError: division by zero | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Karolina Surma <ksurma> |
| Component: | python-robotframework | Assignee: | fedepell <fede> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | fede, jkadlcik, ksurma, mhroncok, pszubiak |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-robotframework-7.0-2.fc40 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-01-28 10:55:19 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: | 2244836 | ||
Opened issue with solution proposal upstream at: https://github.com/robotframework/robotframework/issues/5035 Waiting for feedback to include patch (or a better solution from upstream) FEDORA-2024-c176b80b77 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-c176b80b77 FEDORA-2024-c176b80b77 has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report. |
python-robotframework fails to build with Python 3.13.03. FAIL: test_remove_entries_with_lambda_and_multiple_entries (test_error.TestRemoveRobotEntriesFromTraceback.test_remove_entries_with_lambda_and_multiple_entries) ---------------------------------------------------------------------- Traceback (most recent call last): File "/builddir/build/BUILD/robotframework-6.1.1/utest/utils/test_error.py", line 107, in test_remove_entries_with_lambda_and_multiple_entries self._verify_traceback(r''' ~~~~~~~~~~~~~~~~~~~~~~^^^^^ Traceback \(most recent call last\): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ...<3 lines>... 1/0 ^^^ '''.strip(), assert_raises, AssertionError, raising_lambda) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/robotframework-6.1.1/utest/utils/test_error.py", line 133, in _verify_traceback raise AssertionError('\nExpected:\n%s\n\nActual:\n%s' % (expected, tb)) AssertionError: Expected: Traceback \(most recent call last\): File ".*", line \d+, in <lambda.*> raising_lambda = lambda: raises\(\) File ".*", line \d+, in raises 1/0 Actual: Traceback (most recent call last): File "/builddir/build/BUILD/robotframework-6.1.1/utest/utils/test_error.py", line 106, in <lambda> raising_lambda = lambda: raises() ~~~~~~^^ File "/builddir/build/BUILD/robotframework-6.1.1/utest/utils/test_error.py", line 105, in raises 1/0 ~^~ ZeroDivisionError: division by zero ---------------------------------------------------------------------- Ran 2105 tests in 4.344s FAILED (failures=1) https://docs.python.org/3.13/whatsnew/3.13.html For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.13/fedora-rawhide-x86_64/06936616-python-robotframework/ For all our attempts to build python-robotframework with Python 3.13, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.13/package/python-robotframework/ Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.13: https://copr.fedorainfracloud.org/coprs/g/python/python3.13/ Let us know here if you have any questions. Python 3.13 is planned to be included in Fedora 41. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.13. A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon. We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.