Excerpts from Doug Hellmann's message of 2018-03-28 18:53:03 -0400: > > Because we had some communication issues and did a few steps out > of order, when this patch lands projects that have approved > bot-proposed requirements updates may find that their requirements > and lower-constraints files no longer match, which may lead to job > failures. It should be easy enough to fix the problems by making > the values in the constraints files match the values in the > requirements files (by editing either set of files, depending on > what is appropriate). I apologize for any inconvenience this causes.
In part because of this, and in part because of some issues calculating the initial set of lower-constraints, we have several projects where their lower-constraints don't match the lower bounds in the requirements file(s). Now that the check job has been updated with the new rules, this is preventing us from landing the patches to add the lower-constraints test job (so those rules are working!). I've prepared a script to help fix up the lower-constraints.txt based on values in requirements.txt and test-requirements.txt. That's not everything, but it should make it easier to fix the rest. See https://review.openstack.org/#/c/558610/ for the script. I'll work on those pep8 errors later today so we can hopefully land it soon, but in the mean time you'll need to check out that commit and follow the instructions for setting up a virtualenv to run the script. Doug __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
