On 14 February 2015 at 10:26, Joe Gordon <joe.gord...@gmail.com> wrote: > Digging through the logs this originated from this bug: > https://bugs.launchpad.net/tempest/+bug/1260710 > > Its probably not needed everywhere and in all the clients.
So I've looked more closely at this. Its actually an antipattern. It tells testr that tests are appearing and disappearing depending on what test entry point a user runs each time. testr expects the set of tests to only change when code changes. So, I fully expect that this pattern is going to lead to wtf moments now, and likely more in future. Whats the right forum for discussing the pressures that lead to this hack, so we can do something that works better with the underlying tooling, rather than in such a disruptive fashion? -Rob -- Robert Collins <rbtcoll...@hp.com> Distinguished Technologist HP Converged Cloud __________________________________________________________________________ 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
