d46e9e267d
We need to specify doc requirements in doc/requirements.txt to avoid problems with the pip resolver [1] for the release team [2][3]. Removed specific doc requirements from test-requirements.txt. The problem here is that this repos haven't doc/requirements.txt file and by default in this case zuul will use the test-requirements.txt file to pull requirements [4]. This requirements file contains extra requirements like flake8 that collided with those allowed in our job environment and so the new pip resolver fails to install these requirements and the job exits in error. This project meet the conditions leading to the bug. [1] http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html [3] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html [4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36 Change-Id: Ifa46f9f0b7dca27c9e8a305932141da78b85cd50
17 lines
741 B
Plaintext
17 lines
741 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
# Order matters to the pip dependency resolver, so sorting this file
|
|
# changes how packages are installed. New dependencies should be
|
|
# added in alphabetical order, however, some dependencies may need to
|
|
# be installed in a specific order.
|
|
#
|
|
# Hacking should appear first in case something else depends on pep8
|
|
hacking>=3.0.1,<3.1 # Apache-2.0
|
|
coverage>=4.0 # Apache-2.0
|
|
nodeenv>=0.9.4 # BSD
|
|
selenium>=2.50.1 # Apache-2.0
|
|
testtools>=1.4.0 # MIT
|
|
# This also needs xvfb library installed on your OS
|
|
xvfbwrapper>=0.1.3 #license: MIT
|