You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs installed: action: docs, msg: envreport,cwd: /Users/ssbarnea/rdo/openstack-ansible-os_tempest,cmd: /Users/ssbarnea/rdo/openstack-ansible-os_tempest/.tox/docs/bin/python -m pip freeze,alabaster==0.7.12,Babel==2.6.0,bottle==0.12.16,certifi==2019.3.9,chardet==3.0.4,doc8==0.8.0,docutils==0.14,dulwich==0.19.11,idna==2.8,imagesize==1.1.0,Jinja2==2.10,MarkupSafe==1.1.1,-e git://github.com/openstack/openstack-ansible-os_tempest.git@a3ec7770185beb3fc4816e8915a16abc9fb8c6cb#egg=openstack_ansible_os_tempest,openstackdocstheme==1.29.2,packaging==19.0,pbr==5.1.3,Pillow==5.4.1,Pygments==2.3.1,pyparsing==2.3.1,pytz==2018.9,PyYAML==5.1,reno==2.11.2,requests==2.21.0,restructuredtext-lint==1.3.0,six==1.12.0,snowballstemmer==1.2.1,Sphinx==2.0.0,sphinxcontrib-applehelp==1.0.1,sphinxcontrib-devhelp==1.0.1,sphinxcontrib-htmlhelp==1.0.1,sphinxcontrib-jsmath==1.0.1,sphinxcontrib-qthelp==1.0.2,sphinxcontrib-serializinghtml==1.1.1,sphinxmark==0.1.19,stevedore==1.30.1,urllib3==1.24.1
docs run-test: commands[2] | sphinx-build -b html doc/source doc/build/html
Running Sphinx v2.0.0
connecting events for openstackdocstheme
[openstackdocstheme] connecting html-page-context event handler
making output directory... done
Using openstackdocstheme Sphinx theme from /Users/ssbarnea/rdo/openstack-ansible-os_tempest/.tox/docs/lib/python3.6/site-packages/openstackdocstheme/theme
...
Exception occurred:
File "/Users/ssbarnea/rdo/openstack-ansible-os_tempest/.tox/docs/lib/python3.6/site-packages/sphinxmark/__init__.py", line 151, in watermark
app.info('adding watermark...', nonl=True)
AttributeError: 'Sphinx' object has no attribute 'info'
My impression is that sphuinxmark is not compatible with sphinx 2.x and what makes it worse is that sometimes tox/pip fails to respect version ranges and you end-up using sphinx 2.0 even if your requirements files has a condition to avoid it.
The text was updated successfully, but these errors were encountered:
* Update requirements from branch 'master'
- Bump sphinxmark to 0.2.0
This adds support for Sphinx 2.0 [1] and should fix the OSA jobs.
[1] kallimachos/sphinxmark#33
Change-Id: I21196b787f9e2175939592562756b753992df80a
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
This adds support for Sphinx 2.0 [1] and should fix the OSA jobs.
[1] kallimachos/sphinxmark#33
Change-Id: I21196b787f9e2175939592562756b753992df80a
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
My impression is that sphuinxmark is not compatible with sphinx 2.x and what makes it worse is that sometimes tox/pip fails to respect version ranges and you end-up using sphinx 2.0 even if your requirements files has a condition to avoid it.
The text was updated successfully, but these errors were encountered: