On 11 February 2016 at 16:09, Clark Boylan <[email protected]> wrote: > The reason that I remember off the top of my head is because we spent > far too much time telling people to run `tox -r` when their code failed > during Jenkins testing but ran just fine locally. It removes a > significant amount of debugging overhead to have everyone using a > relatively consistent set of packages whenever they rerun tests.
So for liberty and up, we have constraints which avoid this - every run will be precisely specified once a project has adopted the tox rules. For kilo, if the only reason for -U was to deal with bad lower requirements / missing exclusions for bad releases (which is what I infer from what you recall) then I think we're better off without -U in kilo, because so much of our requirements in kilo are not capped, we're going to face growing breakage as external projects do change things. -Rob -- Robert Collins <[email protected]> Distinguished Technologist HP Converged Cloud __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
