> -----Original Message----- > From: Sean Dague [mailto:s...@dague.net] > Sent: 12 June 2014 17:37 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] Gate proposal - drop Postgresql configurations in > the gate > ... > But if we're talking about a devstack / tempest run, it's not really > applicable. > > If someone can point me to a case where we've actually found this kind of bug > with tempest / devstack, that would be great. I've just *never* seen it. I > was the > one that did most of the fixing for pg support in Nova, and have helped other > projects as well, so I'm relatively familiar with the kinds of fails we can > discover. > The ones that Julien pointed really aren't likely to be exposed in our current > system. > > Which is why I think we're mostly just burning cycles on the existing approach > for no gain. >
In some cases, we've dropped support for drivers in OpenStack since they were not tested in the gate, on the grounds that if it is not tested, it is probably broken. >From my understanding, this change proposes to drop Postgres testing from the >default gate. Yet, there does not seem to be a proposal to drop Postgres >support. Are these two positions consistent ? (Just seeking clarification, I fully understand the difficulties involved in multiple parallel testing at our scale) Tim _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
