python-oslo-log fails to build with Python 3.14.0b2. ============================== Failed 2 tests - output below: ============================== oslo_log.tests.unit.test_rate_limit.LogRateLimitTestCase.test_rate_limit_except_level ------------------------------------------------------------------------------------- Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/usr/lib64/python3.14/unittest/mock.py", line 1427, in patched return func(*newargs, **newkeywargs) File "/builddir/build/BUILD/python-oslo-log-6.1.2-build/oslo.log-6.1.2/oslo_log/tests/unit/test_rate_limit.py", line 87, in test_rate_limit_except_level self.assertEqual(stream.getvalue(), ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^ 'error 1\n' ^^^^^^^^^^^ 'Logging rate limit: drop after 1 records/1 sec\n' ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 'critical 3\n' ^^^^^^^^^^^^^^ 'critical 4\n') ^^^^^^^^^^^^^^^ File "/usr/lib/python3.14/site-packages/testtools/testcase.py", line 421, in assertEqual self.assertThat(observed, matcher, message) ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.14/site-packages/testtools/testcase.py", line 511, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: !=: reference = '''\ error 1 critical 3 critical 4 ''' actual = '''\ error 1 Logging rate limit: drop after 1 records/1 sec critical 3 critical 4 ''' oslo_log.tests.unit.test_rate_limit.LogRateLimitTestCase.test_rate_limit ------------------------------------------------------------------------ Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/usr/lib64/python3.14/unittest/mock.py", line 1427, in patched return func(*newargs, **newkeywargs) File "/builddir/build/BUILD/python-oslo-log-6.1.2-build/oslo.log-6.1.2/oslo_log/tests/unit/test_rate_limit.py", line 59, in test_rate_limit self.assertEqual(stream.getvalue(), ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^ 'message 1\n' ^^^^^^^^^^^^^ 'message 2\n' ^^^^^^^^^^^^^ 'Logging rate limit: drop after 2 records/1 sec\n') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.14/site-packages/testtools/testcase.py", line 421, in assertEqual self.assertThat(observed, matcher, message) ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.14/site-packages/testtools/testcase.py", line 511, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: !=: reference = '''\ message 1 message 2 ''' actual = '''\ message 1 message 2 Logging rate limit: drop after 2 records/1 sec ''' ====== Totals ====== Ran: 187 tests in 1.2868 sec. - Passed: 184 - Skipped: 1 - Expected Fail: 0 - Unexpected Success: 0 - Failed: 2 Sum of execute time for each test: 1.4155 sec. ============== Worker Balance ============== - Worker 0 (94 tests) => 0:00:00.200413 - Worker 1 (93 tests) => 0:00:01.249145 py314: exit 1 (2.22 seconds) /builddir/build/BUILD/python-oslo-log-6.1.2-build/oslo.log-6.1.2> stestr run pid=855 py314: FAIL code 1 (2.23 seconds) evaluation failed :( (2.32 seconds) https://docs.python.org/3.14/whatsnew/3.14.html For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.14/fedora-rawhide-x86_64/09092263-python-oslo-log/ For all our attempts to build python-oslo-log with Python 3.14, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.14/package/python-oslo-log/ 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.14: https://copr.fedorainfracloud.org/coprs/g/python/python3.14/ Let us know here if you have any questions. Python 3.14 is planned to be included in Fedora 43. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.14. 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.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
This is still happening in the de-bootstrap build. ============================== Failed 1 tests - output below: ============================== oslo_config.tests.test_cfg.SubCommandTestCase.test_sub_command_multiple ----------------------------------------------------------------------- Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/builddir/build/BUILD/python-oslo-config-9.6.0-build/oslo.config-9.6.0/oslo_config/tests/test_cfg.py", line 4389, in test_sub_command_multiple self.assertRaisesRegex(argparse.ArgumentError, 'multiple', ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ self.conf, []) ^^^^^^^^^^^^^^ File "/usr/lib64/python3.14/unittest/case.py", line 1414, in assertRaisesRegex return context.handle('assertRaisesRegex', args, kwargs) ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.14/unittest/case.py", line 247, in handle callable_obj(*args, **kwargs) ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/python-oslo-config-9.6.0-build/oslo.config-9.6.0/oslo_config/tests/test_cfg.py", line 98, in __call__ return cfg.ConfigOpts.__call__( ~~~~~~~~~~~~~~~~~~~~~~~^ self, ^^^^^ ...<7 lines>... default_config_dirs=default_config_dirs, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ validate_default_values=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/python-oslo-config-9.6.0-build/oslo.config-9.6.0/oslo_config/cfg.py", line 2187, in __call__ self._namespace = self._parse_cli_opts(argv) ~~~~~~~~~~~~~~~~~~~~^^^^^^ File "/builddir/build/BUILD/python-oslo-config-9.6.0-build/oslo.config-9.6.0/oslo_config/cfg.py", line 3139, in _parse_cli_opts opt._add_to_cli(self._oparser, group) ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/python-oslo-config-9.6.0-build/oslo.config-9.6.0/oslo_config/cfg.py", line 1336, in _add_to_cli subparsers = parser.add_subparsers(dest=dest, title=self.title, description=self.description, help=self.help) File "/usr/lib64/python3.14/argparse.py", line 1948, in add_subparsers raise ValueError('cannot have multiple subparser arguments') ValueError: cannot have multiple subparser arguments ====== Totals ====== Ran: 971 tests in 1.0280 sec. - Passed: 970 - Skipped: 0 - Expected Fail: 0 - Unexpected Success: 0 - Failed: 1 Sum of execute time for each test: 7.3492 sec. ============== Worker Balance ============== - Worker 0 (98 tests) => 0:00:00.723252 - Worker 1 (97 tests) => 0:00:00.815362 - Worker 2 (97 tests) => 0:00:00.836574 - Worker 3 (97 tests) => 0:00:00.905459 - Worker 4 (97 tests) => 0:00:00.835003 - Worker 5 (97 tests) => 0:00:00.634995 - Worker 6 (97 tests) => 0:00:00.804957 - Worker 7 (97 tests) => 0:00:00.839939 - Worker 8 (97 tests) => 0:00:00.805460 - Worker 9 (97 tests) => 0:00:00.507005 py314: exit 1 (3.09 seconds) /builddir/build/BUILD/python-oslo-config-9.6.0-build/oslo.config-9.6.0> stestr run --suppress-attachments pid=854 py314: FAIL code 1 (3.11 seconds) evaluation failed :( (3.19 seconds) error: Bad exit status from /var/tmp/rpm-tmp.BVwEIp (%check)
I just did a scratch build and I don't see this error.
Oh my, that was python-oslo-config, I confused 2 packages. Sorry about the noise.