On 07/22/2016 10:54 PM, Matthew Thode wrote: > One of the things that seems to happen now and then is that an update to > requirements breaks gate for other projects in some way. One thing that > helps is cross project testing, though we do that on a one off basis I'd > like to see this testing become more codified. I have a review out that > does a (very) hackish proof of concept, I've tested both functional and > unit testing, both pass. > > https://review.openstack.org/#/c/345011/ > > (saved the functional testing, don't have the unit test link...) > http://logs.openstack.org/11/345011/5/check/gate-requirements-pep8/5afcdf9/console.html > > So, my question to put to other projects is, which tests of yours do we > hit when requirements break things for you. This list will hopefully be > used to figure out what we can test our changes against to not cause the > badness. > > Any notes on this would be appreciated :D > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > I forgot to mention, but thanks to Ian (sigmavirus) for pointing me to the script I modified for this (came from bandit). -- -- Matthew Thode (prometheanfire)