Created attachment 1564592 [details] Copr build log using python3.8 python-into-dbus-python-0.06-6 fails to build due to failing tests with python 3.8 or 3.7 scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=34681458 pytest output: ============================= test session starts ============================== platform linux -- Python 3.8.0a3, pytest-4.4.1, py-1.8.0, pluggy-0.9.0 -- /usr/bin/python3 cachedir: .pytest_cache hypothesis profile 'default' -> database=DirectoryBasedExampleDatabase('/builddir/build/BUILD/into-dbus-python-0.06/.hypothesis/examples') rootdir: /builddir/build/BUILD/into-dbus-python-0.06 plugins: hypothesis-4.9.0 collecting ... collected 6 items tests/test_signature_parser.py::ParseTestCase::testBadArrayValue PASSED [ 16%] tests/test_signature_parser.py::ParseTestCase::testExceptions PASSED [ 33%] tests/test_signature_parser.py::ParseTestCase::testParsing FAILED [ 50%] tests/test_signature_parser.py::ParseTestCase::testStruct FAILED [ 66%] tests/test_signature_parser.py::ParseTestCase::testUnpacking PASSED [ 83%] tests/test_signature_parser.py::ParseTestCase::testVariantDepth PASSED [100%] =================================== FAILURES =================================== __________________________ ParseTestCase.testParsing ___________________________ self = <tests.test_signature_parser.ParseTestCase testMethod=testParsing> @given(SIGNATURE_STRATEGY) > @settings(max_examples=100) tests/test_signature_parser.py:218: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib/python3.8/site-packages/hypothesis/core.py:568: in execute result = self.test_runner(data, run) /usr/lib/python3.8/site-packages/hypothesis/executors.py:56: in default_new_style_executor return function(data) /usr/lib/python3.8/site-packages/hypothesis/core.py:566: in run return test(*args, **kwargs) tests/test_signature_parser.py:218: in testParsing @settings(max_examples=100) /usr/lib/python3.8/site-packages/hypothesis/core.py:529: in test result = self.test(*args, **kwargs) tests/test_signature_parser.py:229: in testParsing base_type_objects = [ tests/test_signature_parser.py:230: in <listcomp> x.example() for x in \ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = booleans(), random = None def example(self, random=None): # type: (Random) -> Ex """Provide an example of the sort of value that this strategy generates. This is biased to be slightly simpler than is typical for values from this strategy, for clarity purposes. This method shouldn't be taken too seriously. It's here for interactive exploration of the API, not for any sort of real testing. This method is part of the public API. """ context = _current_build_context.value if context is not None: if context.data is not None and context.data.depth > 0: raise HypothesisException( "Using example() inside a strategy definition is a bad " "idea. Instead consider using hypothesis.strategies.builds() " "or @hypothesis.strategies.composite to define your strategy." " See https://hypothesis.readthedocs.io/en/latest/data.html" "#hypothesis.strategies.builds or " "https://hypothesis.readthedocs.io/en/latest/data.html" "#composite-strategies for more details." ) else: > raise HypothesisException( "Using example() inside a test function is a bad " "idea. Instead consider using hypothesis.strategies.data() " "to draw more examples during testing. See " "https://hypothesis.readthedocs.io/en/latest/data.html" "#drawing-interactively-in-tests for more details." ) E hypothesis.errors.HypothesisException: Using example() inside a test function is a bad idea. Instead consider using hypothesis.strategies.data() to draw more examples during testing. See https://hypothesis.readthedocs.io/en/latest/data.html#drawing-interactively-in-tests for more details. /usr/lib/python3.8/site-packages/hypothesis/searchstrategy/strategies.py:280: HypothesisException ---------------------------------- Hypothesis ---------------------------------- Falsifying example: testParsing(self=<tests.test_signature_parser.ParseTestCase testMethod=testParsing>, a_signature='b') You can reproduce this example by temporarily adding @reproduce_failure('4.9.0', b'AAEAAAA=') as a decorator on your test case ___________________________ ParseTestCase.testStruct ___________________________ self = <tests.test_signature_parser.ParseTestCase testMethod=testStruct> > ??? tests/test_signature_parser.py:259: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib/python3.8/site-packages/hypothesis/core.py:568: in execute result = self.test_runner(data, run) /usr/lib/python3.8/site-packages/hypothesis/executors.py:56: in default_new_style_executor return function(data) /usr/lib/python3.8/site-packages/hypothesis/core.py:566: in run return test(*args, **kwargs) tests/test_signature_parser.py:259: in testStruct ??? /usr/lib/python3.8/site-packages/hypothesis/core.py:529: in test result = self.test(*args, **kwargs) tests/test_signature_parser.py:269: in testStruct [x.example() for x in \ tests/test_signature_parser.py:269: in <listcomp> [x.example() for x in \ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = tuples(booleans()), random = None def example(self, random=None): # type: (Random) -> Ex """Provide an example of the sort of value that this strategy generates. This is biased to be slightly simpler than is typical for values from this strategy, for clarity purposes. This method shouldn't be taken too seriously. It's here for interactive exploration of the API, not for any sort of real testing. This method is part of the public API. """ context = _current_build_context.value if context is not None: if context.data is not None and context.data.depth > 0: raise HypothesisException( "Using example() inside a strategy definition is a bad " "idea. Instead consider using hypothesis.strategies.builds() " "or @hypothesis.strategies.composite to define your strategy." " See https://hypothesis.readthedocs.io/en/latest/data.html" "#hypothesis.strategies.builds or " "https://hypothesis.readthedocs.io/en/latest/data.html" "#composite-strategies for more details." ) else: > raise HypothesisException( "Using example() inside a test function is a bad " "idea. Instead consider using hypothesis.strategies.data() " "to draw more examples during testing. See " "https://hypothesis.readthedocs.io/en/latest/data.html" "#drawing-interactively-in-tests for more details." ) E hypothesis.errors.HypothesisException: Using example() inside a test function is a bad idea. Instead consider using hypothesis.strategies.data() to draw more examples during testing. See https://hypothesis.readthedocs.io/en/latest/data.html#drawing-interactively-in-tests for more details. /usr/lib/python3.8/site-packages/hypothesis/searchstrategy/strategies.py:280: HypothesisException ---------------------------------- Hypothesis ---------------------------------- Falsifying example: testStruct(self=<tests.test_signature_parser.ParseTestCase testMethod=testStruct>, sig='(b)') You can reproduce this example by temporarily adding @reproduce_failure('4.9.0', b'AAEAAAA=') as a decorator on your test case ====================== 2 failed, 4 passed in 4.35 seconds ======================
We anticipate making a new release of into-dbus-python upstream which fixes this problem. See related GitHub issue: https://github.com/stratis-storage/into-dbus-python/issues/28.
Thank you, mulhern.
You're welcome! New release is available.
Ilya, please update.
I think I'm the wrong party to ask. I've provided the new upstream release in which the bug is fixed. I think the correct procedure is to close this and package the new release which also has an associated bz: https://bugzilla.redhat.com/show_bug.cgi?id=1719484.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
The coordinated rebuild of Python 3.8 has started in the `f32-python` side tag. If you figure out how to rebuild this package, please don't rebuild it in regular rawhide, but use the side tag instead: on branch master: $ fedpkg build --target=f32-python To wait for a build to show up in the side tag, do: $ koji wait-repo f32-python --build=<nvr> Where <nvr> is name-version-release of the source package, e.g. python-foo-1.1-2.fc32. An updated mock config is posted at: http://copr.fedorainfracloud.org/coprs/g/python/python3.8/ Note that it will take a while before the essential packages are rebuilt, so don't expect all your dependencies to be available right away. Thanks. Let us know if you need up to date info, or if you have any questions. PS this message is mass posted to all the bugs that block the PYTHON38 bug. If this is also a Fedora 31 FTBFS bug and you manage to fix it, you can do a f31 build as usual: on branch f31: $ fedpkg build
Is there anyway that this could be closed and https://bugzilla.redhat.com/show_bug.cgi?id=1719484 just dealt with? There should be no problems in building that new release.
What seems to be the info you need, Yes, this should be delt with. Possibly by updating the package.
I need to know what the process is to get this bz closed and the other bz dealt with, i.e., what is continually preventing that from happening. As soon as I realized there was a problem, I cut a new release, with the expectation that this bz would be closed and the new release would be used for packaging. I did this in June and nothing has happened since, except more updates on this bz. What else can I do?
> I need to know what the process is to get this bz closed and the other bz dealt with, Update the package in Fedora, build it. > i.e., what is continually preventing that from happening. Nobody doing it. > As soon as I realized there was a problem The problem is the package maintainers do not respond here. Ilya, Igor, Andy?
Andy is not working on Stratis (neither in RH anymore), so I doubt he is caring about this package. I don't know why Ilya is not answering. And myself I don't have much time. What about to reassign this package to mulhern?
Yes, that seems best. Please assign the package to me.
The f32-python side tag has been merged. In order to rebuild the package, do it in regular rawhide, but please wait until python3-3.8 is tagged: $ koji wait-repo f32-build --build python3-3.8.0~b3-3.fc32 If your built already started in f32-python, after it is finished, please tag it to rawhide with: $ koji tag-build f32-pending <nvr> For example: $ koji tag-build f32-pending libreoffice-6.3.0.4-3.fc32 Thanks! (This comment is mass posted to all bugzillas blocking the PYTHON38 tracking bug.)
(Python 3.8 has landed in the rawhide buildroot.)
Please transfer maintainership of this package to me.
Version 0.07 release, no point in fixing version 0.06.