Created attachment 1137770 [details] error log Description of problem: ~~~~~~~~~~~~~~~~~~~~~~~ Unit tests from test suite failing on rh-python35-python-docutils. test_parsers/test_rst/test_interpreted test_parsers/test_rst/test_directives/test_code test_parsers/test_rst/test_directives/test_code_long Version-Release number : ~~~~~~~~~~~~~~~~~~~~~~~~ rh-python35-python-docutils-0.12-1.el7 rh-python35-2.0-2.el7 Actual results: ~~~~~~~~~~~~~~~ - the same result on 7.1.z and 7.2.z - log in attachments Expected results: ~~~~~~~~~~~~~~~~~ all pass
This is likely to be a test suite issue rather than a code issue, so not critical for beta.
The issue is most likely derived from upstream. The failing tests get invoked when rh-python35-python-pygments is installed in the system. Since rh-python35-python-docutils does not BuildRequires python-pygments, the specific tests will be disabled during RPM build or manual invoking in environments like mock. However in environments where python-pygments is installed beforehand they will fail, so a user will not be able to build the RPM without disabling the tests. Failure doesn't happen with python-pygments 2.0.2 so it was introduced in 2.1 version upstream. The fastest fix but also a workaround at the moment would be to disable the failing tests through a patch. Also another fix would be to rebase python-pygments to 2.0.2 for GA. The other (and best) way would be to get to the root of the failures that were introduced in 2.1 version and try to figure out a fix upstream but I can't give an ETA for that (maybe it would have to go for next release for that).
Figured out a way to fix the tests, so I will provide a patch. Upstream will need to be contacted as well for this issue as well as the maintainers of this package for fedora.
Created attachment 1154532 [details] Test suite fix
Upstream: https://sourceforge.net/p/docutils/patches/131/
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-2720.html